Ooh, that's a good idea actually. But it doesn't explain this: > If I click enough, I’d eventually see HTTP 503 Service Unavailable. That normally only happe

Ooh, that's a good idea actually. But it doesn't explain this: > If I click enough, I’d eventually see HTTP 503 Service Unavailable. That normally only happens when the reverse proxy has a timeout, which would normally only happen when the backend was completely overloaded. Unless WP has an exponential delay, and the 503 is just the exponential delay becoming longer than the reverse proxy timeout? But why would the main page that the guy is loading say 503, when random non-critical parts like favicon.ico get a 503? Unless the exponential delay is per IP address -- so all the misses to favicon.ico are actually slowing down the main connections past the reverse proxy timeout? EDIT: Actually, no, they have graphs of the server actually spiking memory and CPU usage; you'd expect intentional exponential delay to reduce memory and CPU usage.