Server: performance improvements
(ZBXNEXT-318)
[ZBXNEXT-338] Slow update of IDS tables by db syncers Created: 2010 Apr 29 Updated: 2017 May 31 Resolved: 2010 May 13 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | 1.8.3 |
Type: | Change Request (Sub-task) | Priority: | Major |
Reporter: | Alexei Vladishev | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Comments |
Comment by Alexander Vladishev [ 2010 Apr 29 ] |
14538:20100429:163933.426 Slow query: 262.591837 sec, "update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name=' |
Comment by Alexander Vladishev [ 2010 May 13 ] |
Available in version pre1.8.3, r11965. |
Comment by chloe [ 2011 Sep 29 ] |
Hi, As GDE mentioned on Zabbix forum, this bug is still here in version 1.8.6. During a stress test we obtained lot of slow query and for large amount of services : server crash 27106:20110926:120928.425 Slow query: 120.509592 sec, "update ids set nextid=nextid+256 where nodeid=0 and table_name='events' and field_name='eventid'" GDE quote : our database is a postgresql 9.0.4 hosted on a seperate machine from zabbix server. strangely, this doesn't happen when we test the first 100 hosts. These results have an impact on zabbix. From the frontend, we see a queue for items that are supposed to be checked by zabbix_agent (or internal) that gets ever increasing until the script stop. Thank's in advance |