This work in progress.

2 Performance tuning (

2.1 Hardware

Use fastest processor available

Having more memory is always better

2.2 Operating System

Exclude unnecessary functionality from kernel

2.3 Zabbix configuration parameters

Many parameters may be tuned to get optimal performance.

2.3.1 zabbix_server


General rule – keep value of this parameter as low as possible. Every additional instance of zabbix_server adds known overhead, in the same time, parallelism is increased. Optimal number of instances is achieved when queue, on average, contains minimum number of parameters (ideally, 0 at any given moment). This value can be monitored by using internal check zabbix[queue].


Optimal value is 3.


MySQL only. It is recommended to use DBSocket for connection to the database. That is the fastest and the most secure way.

2.4 Database Engine

This is probably most important part of Zabbix tuning. Zabbix heavily depends on availability and performance of database engine.

2.5 General advices

Example: why use system[procload],system[procload5] andsystem[procload15] if system[procload] contains all.

avoid use of triggers with long period given as function argument. For example, max(3600) will be calculated significantly slower than max(60).

Graphs with alerts