Skip to content
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

question: max concurrent connections? #49

Open
reuzel opened this issue Jan 28, 2016 · 3 comments
Open

question: max concurrent connections? #49

reuzel opened this issue Jan 28, 2016 · 3 comments
Labels

Comments

@reuzel
Copy link

reuzel commented Jan 28, 2016

Hi,

Thanks for this library. For our use-case we have hundreds of thousands of devices connecting to our service. The amount of messages per device is very low: a few per day. This makes that we are more interested in the maximum amount of concurrent connections that can be reached per typical VM (e.g. AWS m3.large running Linux), than how much messages can be send. Your performance wiki page did not mention this. Have you ever done such a test? And if so, would you be so kind to share the results?

With kind regards,
Joost

@vtortola
Copy link
Owner

👍

It should allow you to open connections as long the machine allow you too. My performance tests tried to demonstrate that the component scales up to the max machine's resources, but I have never tried that test. However if you find any issue or limitation let me know, it would be interesting.

Cheers.

@ceeji
Copy link

ceeji commented Mar 17, 2016

I have a similar use case. We want to use this library for a long-time connection environment, for pushing messages to mobile devices. Typically the data is not big and many devices will connect to server(may about 10K-100K) in Linux VM (mono). Any data or benchmark about this? thanks.

@vtortola
Copy link
Owner

Hi!

I did some benchmarking, but in Windows.

https://github.com/vtortola/WebSocketListener/wiki/WebSocketListener-performance-tests

Anyway, if you find any issue let me know. I would be interested in improve it, and I would be happy to help. To be honest, I did similar tests with other .NET components and this was way faster, getting close to the built-in WebSocket.

Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants