Hey, what tips are you talking about? This MUST work on an entry-level hardware. If there is a problem due to inefficiency of ZABBIX code, it will be fixed. But I found it quite strange to suggest hardware upgrades, use of accelerators, whatever even before we know where the problem is. Well, 8xCPU system must be enough for 10-40K of hosts, 1K of hosts is nothing for this kind of hardware.
-
-
Alexei,
I'm seriusly suspicious on Storage. On fisrt step we change ORACLE to MYSQL the things are going better ...
Need u some adicional information about our scenario ? We have apllied our knowledge in this situation but already we have performance issues in some GUI operations.
We can provide any information and do any test (if u ask) to identify where ZABBIX can be better.
[]s,
LucianoComment
-
10-40k hosts shouldn't be a problem for zabbix_server itself, but the database is a whole other issue, long term.
Massive amounts of inserts,updates,deletes tend to screw up indexes a bit. Seperating a decently used webfrontend / zabbix_server from the db tends to give a little more breathing room to the db.
On the subject of accelerators, the 'overview' page (among others) fetches a relative large resultset from the db, and does a lot of parsing. In our case accelerators did help increase responsiveness a bit.Comment
-
What time span are you talking about? 1day, 1 week, 1 month, 3 months, 6 months?
We did several 'short tests' in our own environment, which showed no issues with performance. But our production env gave database performance issues after several months (specially on postgresql and oracle) and i had to switch from postgres to mysql and seperate web-zab from db server.
I'm curious what your testing environment consists of, which components are 'tuned' and how (perhaps i'm missing something in our own env which could increase (db) performance).
(i'm talking about the 1.4 version. testing with 1.5 shows huge improvements
)
Last edited by xs-; 25-08-2008, 10:49.Comment
Comment