For the daring, I am running zabbix frontend 1.4.4 and using zabbix_server 1.5 beta for the collector/poller. I am seeing almost 100% increase in speed due to the database caching in 1.5 zabbix_server engine. This caching is putting lower over head on the database calls. I've been running this setup for about 30 days now and so far no problems. :-) I was also able to bump up the number of pollers to 20 without much impact on the database. Since there were to many problems with the beta 1.5 web frontend, I just ran the 1.4.4 web frontend with the Beta 1.5 Zabbix_Server until the kinks are worked out on the web code. Good job Zabbix developers on the 1.5 Zabbix_Server code, it rocks and is fast. :-)
-
-
For those of you who want to try this, I forgot to mention that you must add a new row to the triggers table as follows.
Table: triggers
Field: type <- this is the actuall name of the field name
Type: int
Default: 0 -
Hmm, that is maybe worth trying. I have a dedicated MySQL server which usually runs with 70%+ CPU usage, just because of Zabbix's MySQL queries.Comment
-
I was having the same issue as well until I started using the 1.5 zabbix_server engine.Comment
-
I am running that here now on our main system (
) however it has not had the desired effect 
The server is still only around 9% idle
Edit: This is with Pre 1.5 (beta) revision 5408 if that makes a difference?Last edited by noxis; 27-02-2008, 18:28.Comment
-
Just a reminder, the trunk code is not for use in production!
Comment
but it was the only way to get it under serious load. I figured out why I was having such high cpu usage despite it being a Quad Core box... I had it set to 200 pollers
Comment