-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max number of connections #30
Comments
SSE is basically a textual broadcast operation. It is usually mostly bound by the amount of data it sends out. If it never has to send any data, the number of clients one can connect is huge (basically, it becomes only bound by the four bytes of comment it needs to send to every client to keep the socket live along proxy servers). I would be very interested in the details of the specific tests you'll run on sc, and I'll try to help if I can. I see no obvious reason why it should be limited to 3000 clients. |
you were right connecting to the server is not the bottleneck, I was able to connect 25.000 concurrent clients with my node.js server, but rather message sending is an expansive operation regarding CPU. |
I will give sc in the next day a try |
@roundrobin Did you manage to further stress test sc? We'd be interested in knowing where the limits are on your hardware compared to other servers. |
How much eventsource clients where you able to connect on one sc instance?
I am right now evaluating different backend servers for EventSource. I was able to connect > 3000 clients through a different node.js backend and send very stable messages to them. But 3000 seems very small to me, if I compare that with other protocols (mqtt, websockets) i tested.
What are the limits you experienced?
The text was updated successfully, but these errors were encountered: