I can check memory comsumption after the holidays. in the meantime you could try to print the numbere of open sockets using http.globalAgent.sockets.length and http.globalAgent.requests.length to see if there is a growing number of requests.
Am 27.12.2012 um 16:54 schrieb Aaron Seet <[email protected]>: > Thanks for the suggestion; i will try that tomorrow. > > However, netstat would not show any existing TCP connection to the backend > server, so I'm not sure if providing a high number would somehow "encourage" > Node to continue opening new connections. Do you notice growing memory leak > with such a setting? > > > thanks, > Aaron > > On Thursday, 27 December 2012 22:01:24 UTC+8, Michael wrote: >> >> Hi Aaron, >> >> I haven't found the solution yet. For the moment my system runs with >> http.globalAgent.maxSockets = 10000 >> I haven't had the problem since then...:) >> >> Maybe this could help you? > > -- > 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 -- 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
