Discussion: Zabbix server performance tweaks.

[burtininkai]

For Zabbix 1.8 I would recommend PostgreSQL 8.3, for Zabbix 1.6 I would go with MySQL 5.1.x. Anyway conversion from one engine to another is quite straight-forward.

Yesterday upgraded server to 1.8. Today finished with proxies upgrade. Current load is 0.3, realy fast, nice work. Alexei could You share some knowledge regarding conversion from MySQL to Postgres?

Thanks for good product

[deploylinux]

Ignore those who recommend putting db on physical host

Put your DB on a separate VM but as long as your hypervisor is not overloaded, there should be almost zero need for dedicated physical server.

Also, historically mysql was better suited for read intensive databases and postgresql for write intensive. Things have changed somewhat as both databases have matured, but a Zabbix monitoring system is highly write intensive and with all the concerns over future of mysql, if you have no preference -- I'd recommend going with postgresql going forward.

[AEckert]

Sizing Example

We are running Zabbix 1.6 on MySQL and Linux using VMWare (3.5) on 2*Quadcore ESX servers using SAN storage.

Number of monitoed hosts 595
Number of monitored items 8897
Number of triggers 4837
Values per seconds 61

We have 2 separate VMs for DB and for Zabbix.
DB: 4GB memory, 4 vCPU, average CPU utilization 75%
Zabbix: 2GB memory, 2 vCPU, average CPU utilization 20%

This configuration works pretty smooth for us.