[mrtg] Re: Suspicious memory usage (leak?) in MRTG 2.15.0
mrtglist at keithbergen.com
mrtglist at keithbergen.com
Thu Dec 21 00:19:43 MET 2006
I run a very simple monitor. It is a custom perl script that monitors the
contents of two folders. I just upgraded to 2.15.0 from 2.14.2, and have
noticed no increase in memory usage. Wperl.exe sat at about 9MB under 2.14.2
and sits now at about 9MB under 2.15.0.
I also use the following which one may expect could cause memory leaks (but
don't seem to):
ThreshProgO[fld_cnt]: c:\mrtg\RCD\gy_bad.bat
ThreshProgOKO[fld_cnt]: c:\mrtg\RCD\gy_good.bat
I hope this helps,
Keith.
-----Original Message-----
From: mrtg-bounce at list.ee.ethz.ch [mailto:mrtg-bounce at list.ee.ethz.ch] On
Behalf Of Volk,Gregory B
Sent: Wednesday, December 20, 2006 12:43 AM
To: mrtg at list.ee.ethz.ch
Subject: [mrtg] Suspicious memory usage (leak?) in MRTG 2.15.0
I recently upgraded to MRTG 2.15.0 on my development (win32) system from
version 2.14.2 and have noticed that the memory footprint for the
related perl executable grows over time. I'm running a pretty typical
config of about 40 targets with LogFormat:rrdtool, and RunAsDaemon:Yes,
so the process never terminates.
I've gone back and observed the per process memory stats while running
2.14.2 on the same system with the same config and have verified that it
maintains a constant memory allocation (Microsoft refers to this metric
as the WorkingSetSize under Perfmon, and it is also listed beneath the
Win32_Process WMI Tree).
I don't think I'm doing anything special that would have caused this
behavior. Nonetheless, I went ahead and killed off just about every
unnecessary process on my dev box to make sure something else wasn't
contributing to this but the problem has persisted.
I placed some graphs at...
http://gvolk.com/20061219_2204_perl_working_set_bytes.png - This is the
amount of memory allocated for the perl.exe binary that the mrtg daemon
is running under. It is a short term (two hour) plot at 60 second
resolution.
and
http://gvolk.com/20061219_1723_memavail_bytes.png - This is the overall
system memory that was available over a 24hour period. I stopped &
started the MRTG daemon at ~23:00 and the system recovered about 40
megabytes of memory. Notice that after 23:00 the memory decreases very
predictably.
I don't know if this is specific to win32 or if it also happens on unix.
I haven't made it over to my dev unix system with 2.15.0 yet. Just
wondering if anyone else is seeing similar behavior.
Thanks
--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive http://lists.ee.ethz.ch/mrtg
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive http://lists.ee.ethz.ch/mrtg
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
More information about the mrtg
mailing list