Number of connections is definitely part of the story.  NodeFly also 
provides graphs of concurrent connections and throughput.

A fuller story might be: If your post-gc heap size goes up but your 
connection count has not, then you may have a memory leak.

-mitch

On Wednesday, November 28, 2012 9:22:02 AM UTC-8, Felix E. Klee wrote:
>
> On Wed, Nov 28, 2012 at 6:16 PM, themitchy <[email protected]<javascript:>> 
> wrote: 
> > If this post-gc value continues to increase, you likely have a memory 
> > leak. 
>
> Doesn't make sense to me. I expect that value to fluctuate with the 
> number of client (browser) connections. 
>

-- 
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

Reply via email to