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

Memory usage under load #62

Closed
majek opened this issue May 2, 2012 · 3 comments
Closed

Memory usage under load #62

majek opened this issue May 2, 2012 · 3 comments

Comments

@majek
Copy link
Member

majek commented May 2, 2012

Some people suggest sockjs-node is not very good in terms of memory usage:

I did a few simple benchmarks and it went well. Under real load it seems to be performing well, but the memory usage is a bit high ( ~400 MB for 1000 connections)!

We should investigate what's happening.

@3rd-Eden
Copy link

WS has been struggling with the same issues.. So you might find some information / points to investigate at the related issue: websockets/ws#43

@nicokaiser
Copy link

(As noted in websockets/ws#43) This may be an issue of node.js not giving back memory to the OS early (only if it's really needed). So maybe this is not a leak, but "only" stupid GC.

Did you test 1,000 connections on a machine with less than 400 MB memory? Does it start to swap or crash?

@theyak
Copy link

theyak commented Oct 4, 2012

How do you load test many connections?

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

No branches or pull requests

5 participants