If I remember correctly, I had the same problem when using socket.io with 
the default memory store. 
now I use redis and did some manual cleaning. It has been running for more 
than 3 month with high traffic and stable memory.

you can check this thread in here 
https://github.com/LearnBoost/socket.io/issues/463

and this 
https://github.com/LearnBoost/socket.io/issues/831

Or move to SockJS ( it still has its own issues but might be better)

Joe




On Monday, August 5, 2013 5:17:14 PM UTC-7, [email protected] wrote:
>
> Hi,
>
> Memory graphs (memory shown in MB):
>     http://i.imgur.com/gMwYSWS.png
>     http://i.imgur.com/gLF5NNr.png
>
> Node version: 0.10.15 (same issue applies on 0.8.*, 0.10.15 and under)
>
> I've been trying to tackle a serious memory issue for my web application, 
> https://kiwiirc.com/
> The project consists of mainly incoming SSL connections via socket.io and 
> lots of outgoing TCP (plaintext/TLS) connections.
>
> I have been running a test server with a % of live traffic heading to it 
> to produce the memory graphs given above.
> The heap does not have a significant rise and the GC does bring it down as 
> evident in the graph.
> However, the RSS memory usage has clearly gone out of control. Eventually 
> it starts swapping on the system until the process is killed due to memory 
> usage.
>
> What can I do to debug this RSS memory issue? Are there any known issues 
> that would cause this?
>
> Darren
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to