You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
(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?
Some people suggest sockjs-node is not very good in terms of memory usage:
We should investigate what's happening.
The text was updated successfully, but these errors were encountered: