Ideas:
1, analysis of the reasons for the slow
2. Optimization from Zabbix itself
3, from the MySQL aspect optimization
Environment Description:
Cloud Host (1 units): 4G memory, 2Mbps bandwidth, 500G HDD, 2-core cpu,centos6.5 64bit
Zabbix version 2.2.1
MySQL version 5.1.73
Host about 250 units
Itmes 120 pcs/Set
Zabbix and MySQL are the default configurations
Slow performance:
1, the front-end in the overview is particularly slow to view
2. Slow in batch modification
Note: "Slow" is a feeling and a threshold, and when you or your boss can't stand it, you need to improve
Reasons for Slow:
1, the data volume is large, the display when the query from the database time-consuming.
2, the database read and write slow, resulting in long query time
For the "large amount of data", in fact, there is no good way, with the host and items increase, will be more and more large. What can be done is to reduce the speed of getting bigger.
1, for items to reduce The history storage period items and trend storage period value, specifically what and effect first leave a question (mainly is not looking at the document, back up)
2, for/etc/zabbix_server.conf to increase the value of Maxhousekeeperdelete, will delete some data, specifically what and how to delete the first to leave a question (mainly that they have not looked at the document, back up)
3, directly into the database delete (not recommended)
Optimized for database (I'm using MySQL):
Objective: To increase the reading and writing speed of MySQL (at this time, the relationship with Zabbix is not big, mainly msyql knowledge. )
Method: MySQL One master one from +amoeba, Master writes from read.
Detailed MySQL, amoeba configuration is being collated ...
This article is from the "Linux starter practiced hand Essentials" blog, so be sure to keep this source http://3090804.blog.51cto.com/3080804/1714657
Zabbix turn on slow causes and optimization attempts