We couldn't delete histories in Zabbix because
our innodb_buffer_pool_size was equal to 256M. Increasing to 4G, I was able to remove the CPU user time item history (with thousands of records for almost a year and 1 minute interval).
However, the removal lasted 27 minutes (i clocked).
What could I do to increase the speed of removal?
Our housekeeper is still disabled. When I activate, will I have problems even with innodb_buffer_size 4G?
follow the data for analysis:
VM Zabbix
RAM: 8GB (I will increase to 16GB);
CPU 4;
Monitoring of 860 hosts;
Active Items 8676;
Innodb_buffer_size: when I increase the RAM to 16GB, I also think of increasing this to 12GB;
our innodb_buffer_pool_size was equal to 256M. Increasing to 4G, I was able to remove the CPU user time item history (with thousands of records for almost a year and 1 minute interval).
However, the removal lasted 27 minutes (i clocked).
What could I do to increase the speed of removal?
Our housekeeper is still disabled. When I activate, will I have problems even with innodb_buffer_size 4G?
follow the data for analysis:
VM Zabbix
RAM: 8GB (I will increase to 16GB);
CPU 4;
Monitoring of 860 hosts;
Active Items 8676;
Innodb_buffer_size: when I increase the RAM to 16GB, I also think of increasing this to 12GB;
Comment