Up.time Core Service – Thread Pool Backlog

by Mar 24, 2011

I was under the impression that up.time core service should be able to handle a load 25 monitors per second, my instance is only running approximately 15 monitors per second and with that load it is unable to withstand 3 hours of run time before the queuing backlog of requests is in a unrecoverable state.

So far the only way to recover from this queue backlog is to reduce polling frequency for several monitors or to reload the core service.

Has anybody else experienced this same issue with the uptime core service?

Our Server
2 x Dual Core 2.5 GHz, 16Gig Ram, Linux RHEL AS release 4