What's the worst polling-rate config you've ever inherited?
Reading a recent case study about a Las Vegas casino resort whose Building Management System was bogging down across 780 devices. Daily reboots. Missed schedules. Team was ready to replace hardware.
Turned out the network was running on a global "fast policy" hammering data requests roughly every second. Dialing it back to 10 or 60 seconds took the Network Health Score from 40% to 81% overnight. No hardware replaced.
It made us wonder how often this is happening quietly. Polling settings get inherited from previous integrators or copy-pasted from earlier projects, and nobody questions them until something breaks.
So: what's the worst polling configuration you've inherited or discovered? Bonus points for the ones where the original logic is genuinely lost to history.
Case study for context: https://www.optigo.net/projects/case-study-gaming-casino/