Hi Brad:

On 2/14/08, Brad Nicholes <[EMAIL PROTECTED]> wrote:

> Basically it is just the standard configuration with gmond reporting 
> bytes_in, bytes_out, pkts_in, pkts_out metrics.  As part of these metric 
> gathering functions, interface names needed to be added to a hash table.  
> Each time the metric function was called and the /proc/net/dev file was 
> parsed, the interface names that were found in the file were strdup'ed() and 
> attempted to be added to the hash table.  The problem is that the strdup'ed 
> string only needed to be added once, however the name was being strdup'ed 
> every time whether it was actually added to the hash table or not.  On the 
> attempts when the name already existed, the strdup'ed memory was never freed.
>
>  Basically, you just have to watch the memory footprint for gmond grow over 
> time.  It doesn't happen very fast.

Right -- so this doesn't appear to have anything to do with gmond's
configuration (mute/deaf), it just grows over time.

I just checked a gmond that has been running for 190 days, and RSS is
150MB -- not good...

Glad that we tracked this issue down.

Cheers,

Bernard

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to