Testing Observium, I've noticed that polling an EX4200/4550 with Observium takes about 200 seconds. There are around 300 ports, and I've noticed that Observium polls the logical interfaces as separate from the physical interfaces. I considered disabling logical interface polling, but the logical interfaces are used for a lot of port correlations, etc.
Cacti with Spine takes 13 seconds to poll everything in our network, and Cacti with the PHP poller takes maybe 2 minutes to poll everything in our network.
Because of Cacti's ability to handle this particular device (even with its PHP poller), I'm pretty convinced that the issue isn't the device.
I've checked interface, memory, and CPU utilization on the Observium server as well as the device and the network in-between. Everything is fine. I've also turned Cacti off to ensure there was no strange clash. I also turned polling off for all ports that were in a "down" state and disabled those ports in the switch as well.
It almost seems that Observium's poller walks one OID at a time in serial, or otherwise does some ridiculously complex discovery on every poll that it doesn't need to do. Cacti does bulk requests, so it gets around 50 OIDs per request to the switch stack.
Is it possible that I'm missing something in the Observium configuration?
Thanks!
--Tyler