Live data from Hacker News

Show HN: 2M fully loaded concurrent WebSockets

oatpp.io

31–32 of 32 posts

Re: Show HN: 2M fully loaded concurrent WebSockets

#31
post #8

Earlier quoted context omitted.

Not 20M, but 2M fully loaded sockets... about 1 message per 13sec per Connection

I might of missed it, but didn’t see in the article any mention of multiple IPs or NICs isn’t the theoretical maximum 65k ports per IP?

No, the tuple includes source ip and port as well.

Re: Show HN: 2M fully loaded concurrent WebSockets

#32

Earlier quoted context omitted.

Ah. Thanks guys.

I'll fill in some more things. They didn't have the bloat back then that we have these days, like the crazy deep call stacks you see in both object-oriented and functional programming. CICS programs were frequently written in assembler, sometimes COBOL and PL/I. Mainframe compilers from the early 1970s were much more advanced in many ways than the Unix/C technology described in the Dragon Book. The mainframe did I/O…

Thanks for elaborating more. I think people who do performance work constantly rediscover or re-invent this (ie like the websocket post).
Post reply on HN