News for hackers. Stuff that matters.
Re:A self-killing web site requested by a customer (2011) by sneak on Thursday May 07, 2020 @07:50AM (#23101934)
System latency is not linear with load. At a certain threshold it starts swapping way beyond the capacity of the disk i/o and basically nothing gets done.

I would assume that if you left it alone for an hour or so it might eventually unfuck itself, but for production purposes, that counts as dead, especially when you can’t even ssh into it because the memory allocations for your ssh session are also in that gigantic queue for disk bandwidth via swap.

Re:A self-killing web site requested by a customer (2011) by MaxBarraclough on Thursday May 07, 2020 @08:22AM (#23102157)
Why doesn't the server just drop incoming requests until it's able to handle them again? As I mentioned in another comment, this is what routers do.

edit I hadn't noticed this at the bottom of the article:

> they could have rewritten their web site code so it didn't send the machines into a many-GB-deep swap fest. They could have done that without getting any hosting people involved. They didn't

Re:A self-killing web site requested by a customer (2011) by rovr138 on Thursday May 07, 2020 @09:55AM (#23102973)
Apache has a way to limit the amount of processes. Tuning that would have helped.