alt Hacker News> What I had missed is that we deployed a new internal service last week that sent less than three GetPostRecord requests per second, but it did sometimes send batches of 15-20 thousand URIs at a time. Typically, we'd probably be doing between 1-50 post lookups per request.
That’ll do it.
Replies
jandrese • today at 6:58 PM
The incredible part about this is because their backend is all TCP/IP they were literally exhausting the ports by leaving all 65k of them in TIME_WAIT, and the workaround was to start randomizing the localhost address to give them another trillion ports or so.
➕ show 1 reply
bombcar • today at 4:31 PM
Zero, one, many, many thousands.
LoganDark • today at 7:03 PM
And then they fix the issue by using multiple localhost IPs rather than, perhaps, not sending 15-20 thousand URIs at a time
➕ show 1 reply
htx80nerd • today at 6:28 PM
less than ideal if I had to be frank.
Ahh, the three relevant numbers in development: 0, 1, and infinity.