[2.0rc1] High cpu load with postgresql monitoring 5000 snmp items

[c.mammoli]

Hi, I'm using postgresql and the new 2.0 low level discovery to monitor some switches.

Everything is fine with most of them, the items are discovered and monitor fine without high load on the server. But one is a 9 unit stack with hundreds of ports.

After discovery I have 5173 items and 2792 triggers. The database starts to eat CPU (more than 80% all the time) and the zabbix queue starts to fill up losing events...

The very strange thing is that this happens even if I keep all the items disabled!!! Just adding them to the host kills the db.

This didn't happen with 1.8 monitoring the same items (with a script generated template)

The server is a vmware virtual machine with 2GB of ram and 2 vCPU

Number of hosts (monitored/not monitored/templates) 129 47 / 0 / 82
Number of items (monitored/disabled/not supported) 13445 4101 / 8768 / 576
Number of triggers (enabled/disabled)[problem/unknown/ok] 3288 3282 / 6 [39 / 0 / 3243]
Required server performance, new values per second 66.86 -

[c.mammoli]

Solved, I wrongfully set a flexible interval of 50 seconds on the discovery rule. An snmpwalk of thousands of items every minute was a bit too much for the db.