If you have a browser sitting on e.g. a screen with lots of graphs and the browser's route to the zabbix web server goes away for a period of time, refresh requests appear to queue up more or less without bound. When the route is restored these dequeue at a very rapid rate and can pretty effectively DOS all of zabbix with a severe IO overload. There really should be a bound on how many requests get queued up.