I retract my earlier statement about our performance problems going away. They've returned.
The utter randomness of Zabbix's behavior, the lack of consistent performance, are causing me and my company a lot of pain. We've upgraded to a larger server, configured a custom MySQL server with multiple I/O paths to handle the heavy database load, and all that was working OK -- not great, still a lot of random behavior, but tolerable. The 1.8 upgrade, for us, increased resource utilization by a factor of 5x - 10x. Totally unacceptable.
Here's a graph (I do love the new graphs in 1.8, that's a positive comment) of our CPU utilization over the past month, I've shown where we did upgrades and/or changes:

We're getting very close to throwing Zabbix away entirely. It's behavior is simply not reliable & consistent, and that is not what we want in a monitoring product. We're looking at support options, but I'm having a lot of trouble convincing my management to spend $4000 or $8000 a year on something that's already not somewhat stable & reliable.
The utter randomness of Zabbix's behavior, the lack of consistent performance, are causing me and my company a lot of pain. We've upgraded to a larger server, configured a custom MySQL server with multiple I/O paths to handle the heavy database load, and all that was working OK -- not great, still a lot of random behavior, but tolerable. The 1.8 upgrade, for us, increased resource utilization by a factor of 5x - 10x. Totally unacceptable.
Here's a graph (I do love the new graphs in 1.8, that's a positive comment) of our CPU utilization over the past month, I've shown where we did upgrades and/or changes:

We're getting very close to throwing Zabbix away entirely. It's behavior is simply not reliable & consistent, and that is not what we want in a monitoring product. We're looking at support options, but I'm having a lot of trouble convincing my management to spend $4000 or $8000 a year on something that's already not somewhat stable & reliable.

Comment