[ZBXNEXT-1162] Zabbix backend performance tuning Created: 2012 Mar 22 Updated: 2012 Mar 29 Resolved: 2012 Mar 22 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 1.9.9 (beta) |
Fix Version/s: | 2.0.0 |
Type: | Change Request | Priority: | Major |
Reporter: | Alexander Vladishev | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | performance | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Comments |
Comment by Alexander Vladishev [ 2012 Mar 22 ] |
Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1162 |
Comment by richlv [ 2012 Mar 24 ] |
any more information on what exactly was improved regarding the processing of the triggers ? <zalex> yes, the issue cannot be closed without the answer to this question <dimir> Basically there are 2 improvements:
Am I right, sasha? <Sasha> You are absolutely right! |
Comment by dimir [ 2012 Mar 28 ] |
Successfully tested! Please review my small style fixes in r26455. |
Comment by dimir [ 2012 Mar 28 ] |
(1) Wait, there is one issue with trigger update but need to collect more information. <dimir> So if the trigger status is PROBLEM and we update the trigger after that we will not get recovery message when trigger goes to OK state. I guess this is by design. CLOSED |
Comment by dimir [ 2012 Mar 29 ] |
Successfully tested, do not forget to review my small changes in r26455. <Sasha> Thanks! CLOSED |
Comment by Alexander Vladishev [ 2012 Mar 29 ] |
Fixed in version pre-2.0.0rc3 r26477. |