[ZBX-4815] IT Services fails to load with big count of them Created: 2012 Mar 28 Updated: 2017 May 30 Resolved: 2012 Dec 16 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 1.8.9, 1.8.12 |
Fix Version/s: | 2.0.0rc4 |
Type: | Incident report | Priority: | Major |
Reporter: | Alexey Pustovalov | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Labels: | itservices, performance | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
MySQL |
Attachments: | sla_configuration.zip sla_monitoring.zip zbx_services.gz | ||||||||
Issue Links: |
|
Description |
If IT Services have a lot of services configured and services tree is very branched, then Zabbix frontend processes the tree, triggers and other resources very long time. Additionally, Configuration IT Services page is very large! I attached the sql dump with tables related to IT Services for this problem. The sql dump contains about 8000 services:
----------
---------- |
Comments |
Comment by Oleksii Zagorskyi [ 2012 Mar 28 ] |
Here is two aspects of the problem: web server and browser. Web server and SQL server are very loaded because crazy count of queries perform. Another aspect - browser. Some browsers very busy on page load: Firefox, Safari, Chrome |
Comment by Pavels Jelisejevs (Inactive) [ 2012 Mar 29 ] |
May be I'll be able to do something about it while working on <zalex> I think would be better as separate issue. <Sasha> <pavels> Ah, sorry, haven't noticed that it's a 1.8 issue. |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 02 ] |
I'll use this issue to improve the performance of the IT service configuration page in 2.0. The monitoring page will be handled in REOPENED. |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 02 ] |
(1) When I try to delete a host with triggers with enabled debug mode, PHP runs out of memory in update_services_rec( ). <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 03 ] |
(2) If the "Do not calculate" algorithm is is selected in the service configuration form, all of the SLA-related and trigger fields should be disabled. <pavels> RESOLVED. <Vedmak> if services has "Do not calculate" algorithm, when we open it for editing, SLA field is not disabled. Also when change algorithms, SLA field can be enabled without checked checkbox. <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 08 ] |
(3) Forbid deleting services with hardlinked children. <pavels> RESOLVED. <Vedmak> edit form for such services still have "Delete" button. <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 09 ] |
(4) The dependency selection pop up now supports multiselect. RESOLVED. <Vedmak> CLOSED |
Comment by Alexey Fukalov [ 2012 May 09 ] |
(5) <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Alexey Fukalov [ 2012 May 09 ] |
(6) <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Alexey Fukalov [ 2012 May 09 ] |
(7) <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Alexey Fukalov [ 2012 May 10 ] |
(8) <pavels> RESOLVED. <Vedmak> CLOSED |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 11 ] |
Available in trunk r27450. CLOSED. |
Comment by Pavels Jelisejevs (Inactive) [ 2012 May 11 ] |
A couple of words about what has been done: the fix greatly reduces the load on the database, though the overall performance of the page is still poor. It also fixed some issues that were caused by the large amount of services, e.g. frontend running out of memory when trying to delete a trigger linked to a service. A lot of time is needed to render the HTML of the tree itself, and fixing that will require some time, so now we'll have to leave it for later. |
Comment by Oleksii Zagorskyi [ 2012 May 11 ] |
Some fixes/improvements it's good but I'm afraid the issue in not solved. |
Comment by Alexey Pustovalov [ 2012 May 11 ] |
SQL queries already much better but a time load data from IT services for monitoring and configuration pages remains at the same level. |
Comment by richlv [ 2012 Dec 14 ] |
how about a new issue for this ? initial improvements were done before 2.0.0 was out, and now this issue is stretching past 2.0.4 already... |
Comment by Alexey Pustovalov [ 2012 Dec 16 ] |
I'm closing the issue. All new bugs should be solved in new issues. |