This is an amazing writeup. I have run into this before (running out of sockets) stress testing a web proxy, and when I did, I cursed the TCP designers for des

This is an amazing writeup. I have run into this before (running out of sockets) stress testing a web proxy, and when I did, I cursed the TCP designers for designing only 32 bit sequence numbers and 16 bit port numbers. That said, maybe there is still a need for TIME_WAIT in a distributed protocol that can't guarantee sequence number uniqueness 100%. I'm glad the article provided detailed cpu and memory measurements explaining their costs, which don't seem too bad. It's running out of tuples due to a practically arbitrary and short-sighted limit that is the killer. Also liked the interesting notes about socket linger.