Hard
TIME_WAIT and ephemeral ports under high connection churn
A high-throughput proxy opens thousands of short-lived outbound TCP connections per second to backend servers, and the proxy itself always calls close() first on each connection right after reading the backend's response. Which side of each connection enters TIME_WAIT, and why does this specifically threaten the proxy rather than the backend with resource exhaustion?
21 of 45 in Networking