4 ms·
And even if you've got a really good idea of how many connections you can handle at a time, when problems start happening the patterns might change. For exampl
by michaelt 7y ago
And even if you've got a really good idea of how many connections you can handle at a time, when problems start happening the patterns might change.
For example, maybe in the average second you see 1 login request (CPU-bound password hashing), 10 page views (database connection bound), 100 image views (IO/client speed bound), and 0.01 login sessions being bounced between servers (???? bound). And your server is limited to 111 connections per second.
But when the site goes down? Users can't load images until they've seen pages, and can't see pages until they've logged in, so now you're processing 111 login attempts per second when your tuning assumed a fraction of that.