I have a database where the number of rows in the alarms table is 455,000. When I click on the monitoring button it takes forever for the page to come up. If I click on the datetime on last change php runs out of memory or time allocated for scripts.
The query being run is "select * from alarms where triggerid=12221 order by clock desc"
Apparently once zabbix has this recordset it further tries to mangle it, filter it, or do something in order to display it. Either way it crashes consistently.
I would suggest some other refining of the whereclause or perhaps a limit clause.
The query being run is "select * from alarms where triggerid=12221 order by clock desc"
Apparently once zabbix has this recordset it further tries to mangle it, filter it, or do something in order to display it. Either way it crashes consistently.
I would suggest some other refining of the whereclause or perhaps a limit clause.