Show HN: 2M fully loaded concurrent WebSockets

#1

Post by lganzzzo » Tue, May 07, 2019, 1:01 AM UTC

Show HN: 2M fully loaded concurrent WebSockets
oatpp.io

Re: Show HN: 2M fully loaded concurrent WebSockets

#2

Post by PaulHoule » Tue, May 07, 2019, 1:09 AM UTC

Reminds me of the good old days when an IBM 360 running CICS could support 13,000+ terminals with just 16 MB of RAM.

I thought shoehorning was a microcomputer thing until I found out about that!

Re: Show HN: 2M fully loaded concurrent WebSockets

#3

Post by lganzzzo » Tue, May 07, 2019, 1:18 AM UTC

PaulHoule wrote: post #2

Reminds me of the good old days when an IBM 360 running CICS could support 13,000+ terminals with just 16 MB of RAM. I thought shoehorning was a microcomputer thing until I found out about that!

I Agree, It could be less than 15Gb for 2M WebSockets. But it's the first benchmark, and I decided to make it without much of optimizations - just to have a starting point. There is still much space for optimizations like reducing internal buffers and so on, but I will leave it for future tests.

Re: Show HN: 2M fully loaded concurrent WebSockets

#4

Post by chirau » Tue, May 07, 2019, 1:46 AM UTC

Get your credit card or your infra ready, whichever applies... someone seating here with me is about to max out botnet rush to you

Re: Show HN: 2M fully loaded concurrent WebSockets

#5

Post by lganzzzo » Tue, May 07, 2019, 1:51 AM UTC

You may also want to check out:

- benchmark project repo - https://github.com/oatpp/benchmark-websocket

- oatpp framework repo (the benchmark built with) - https://github.com/oatpp/oatpp

Re: Show HN: 2M fully loaded concurrent WebSockets

#6

Post by iandanforth » Tue, May 07, 2019, 1:52 AM UTC

I'm confused. If there are 20M clients and the server is sending 9M messages per minute, doesn't that mean that each client is sending less than 1 message per minute?

Re: Show HN: 2M fully loaded concurrent WebSockets

#7

Post by lganzzzo » Tue, May 07, 2019, 1:54 AM UTC

chirau wrote: post #4

Get your credit card or your infra ready, whichever applies... someone seating here with me is about to max out botnet rush to you

:)) My infra is $15/Month instance running oatpp server

Re: Show HN: 2M fully loaded concurrent WebSockets

#8

Post by lganzzzo » Tue, May 07, 2019, 1:58 AM UTC

iandanforth wrote: post #6

I'm confused. If there are 20M clients and the server is sending 9M messages per minute, doesn't that mean that each client is sending less than 1 message per minute?

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

Re: Show HN: 2M fully loaded concurrent WebSockets

#9

Post by Thaxll » Tue, May 07, 2019, 2:41 AM UTC

The memory seems high actually, I've seen other C / C++ / Go implementation using less than a 1GB for 1m connections. Pretty cool nonetheless!

https://github.com/uNetworking/uWebSockets

https://speakerdeck.com/eranyanay/going-infinite-handling-1m...

Re: Show HN: 2M fully loaded concurrent WebSockets

#10

Post by lganzzzo » Tue, May 07, 2019, 3:04 AM UTC

Thaxll wrote: post #9

The memory seems high actually, I've seen other C / C++ / Go implementation using less than a 1GB for 1m connections. Pretty cool nonetheless! https://github.com/uNetworking/uWebSockets https://speakerdeck.com/eranyanay/going-infinite-handling-1m...

Thanks, In this benchmark I decided to go without much of the framework tuning. Mostly took it as is in order to see what I can get. In any case oatpp is general purpose web framework, it is understood that dedicated libraries like uWebSockets may be more optimized. Nevertheless I beleve it's still much space for tunning and optimizing of oatpp.