3 ms·
FWIW terrible example, that's why Apache is always blowing up when it gets much load. I'd much rather a server service all requests properly than fail. Then yo
by axod 17y ago
FWIW terrible example, that's why Apache is always blowing up when it gets much load.
I'd much rather a server service all requests properly than fail. Then you can measure the load yourself, and load balance appropriately, knowing that all requests are being serviced properly.
- jbert 17y ago> I'd much rather a server service all requests properly than fail. Depends what you mean by "properly". If you mean "within N seconds", then when overload takes you over the point at which reqs take N seconds, all your reqs are now failing to be served properly. Whereas if you have a cap at M concurrent reqs (which you calculate so that your platform can service each of those M reqs within N secs), you get to handle M concurrent reqs properly under overload. So, not under overload - same behaviour. Under overload, a cap allows M concurrent reqs to be handled properly, no cap allows none. What alternative are you suggesting? Let the platform run slower as load increases until your alarm system pings you at a threshold and you then provision more servers?