Neon is routinely at 0% idle CPU when looking at realtime info. Even after manually turning down some of the most CPU-expensive checks, the remaining load still routinely spiked the machine to 0% idle CPU, so in its normal config it's definitely well past the line.

Also, the main icinga process itself is single-threaded and routinely locks up a single CPU core, effectively running out of processing power to keep up with its own demands, even if other cores are idle.

I noticed this while debugging the intermittent ipv6 monitor failures. I really don't know if this is casual or even related, but I figure solving this basic issue seems prudent...