RE: snmptrapd with attached perl script eats all memory

	It is a common misconception that "memory usage" reports can be relied upon to report the amount of memory currently in use by an application.  This is not necessarily the case, as lazy garbage collection by the OS can result in it appearing that a process is using dramatically more memory than is in fact in use.  This can be the case if the process is performing a lot of OS level dynamic memory allocation - the OS will often hand it new pages even when it has freed a lot of pages.  This process will generally continue until RAM is "filled", but the OS will garbage collect before swapping, so the process will "max out" at some apparently high level of memory usage, even though it is using much less memory than appears on the monitor.  The acid test is to start up more applications, prefer
 ably ones that use a fixed but significant amount of memory (JVMs are handy here), and see if swapping occurs.


	HTH,

Mike

-------------------------------------------------------------------------
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/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users