Hi
I supose that there are many posts about tunning both zabbix and mysql I followed many of them and also checked other Mysql tunning posts and articles on other sites. But this is currently a Zabbix question
After some tunning on MySQL and reduced the number of items and their polling frequecy as well as the history to keep the DB not so huge, I'm still facing something that I dont't understand.
My current setup is using 5 minutes polling interval (60secs in few items and more time in others) with a history of 7 days. I setup houskeeper to cleanup any item older than 7 days from history. Currently my setup reports is monitoring about 860 items, and reports 7.5 new values per second (Although my server is a little one this is far away of the 3000 nvps I seen on some examples).
Well with 856 items =~ 860 items monitored each 5 minutes (average) this leaves me about a 860 items x 7 days x 24 x hours x 60 minutes / 5 minutes poll = 1733760 historic values
Or if I use the new values per second (~7.5) this gives me 7.5 values x 60 secs x 60 minutes x 24 hours x 7 days = 4536000 for the historic values
Currently my history_unit table is about 28 Millions of Rows, which is far away much more than any of the estimated number of values.
I already tried to cleanup old values manually deleteing rows with clock before 7 days and even orphaned itmes, but the table indeed contains 28Millions of Rows.
Why is zabbix using too many rows?
I supose that there are many posts about tunning both zabbix and mysql I followed many of them and also checked other Mysql tunning posts and articles on other sites. But this is currently a Zabbix question
After some tunning on MySQL and reduced the number of items and their polling frequecy as well as the history to keep the DB not so huge, I'm still facing something that I dont't understand.
My current setup is using 5 minutes polling interval (60secs in few items and more time in others) with a history of 7 days. I setup houskeeper to cleanup any item older than 7 days from history. Currently my setup reports is monitoring about 860 items, and reports 7.5 new values per second (Although my server is a little one this is far away of the 3000 nvps I seen on some examples).
Well with 856 items =~ 860 items monitored each 5 minutes (average) this leaves me about a 860 items x 7 days x 24 x hours x 60 minutes / 5 minutes poll = 1733760 historic values
Or if I use the new values per second (~7.5) this gives me 7.5 values x 60 secs x 60 minutes x 24 hours x 7 days = 4536000 for the historic values
Currently my history_unit table is about 28 Millions of Rows, which is far away much more than any of the estimated number of values.
I already tried to cleanup old values manually deleteing rows with clock before 7 days and even orphaned itmes, but the table indeed contains 28Millions of Rows.
Why is zabbix using too many rows?
Comment