topic Re: top command question in Operating System - HP-UX

Re: top command question

A. Clay Stephenson — Mon, 02 Jun 2003 20:28:50 GMT

The reason that the value is approximate is that memory calculations are very tricky because of shared libraries and shared memory segments. Consider the simple case of the shell: There might be hundreds of instances of sh running each with it's own private data segment but sharing a common text segment - the executable code and sharing functions in shared libraries. How many times should that memory usage be counted? It's even possible for the total memory to greatly exceed the virtual memory of the box but that's an illusion because of the sharing of memory segments.

Re: top command question

S.K. Chan — Mon, 02 Jun 2003 20:34:48 GMT

In addition read the HP Memory Mgt Whitepaper.
http://docs.hp.com/hpux/onlinedocs/os/11i/mem_mgt.html

Re: top command question

James R. Ferguson — Mon, 02 Jun 2003 21:16:32 GMT

Hi:

To add to the information already given, a recent 11.0 patch corrected an incongruous reporting of memory usage by 'top'.

Without PHCO_26020, 'top' could sometimes show the RESident size of a process as larger than its SIZE. This was due to the inclusion private uarea, shared memory, mmap regions in addition to the resident data, stack and text allocated, in the calculation of RES. The patch "resolves" the anomoly by adding these values to the SIZE. Again, this emphasizes why the RESident value is only an approximation.

Regards!

...JRF...