Operating System - HP-UX
1828370 Members
3033 Online
109976 Solutions
New Discussion

Re: How to display/monitor application use of memory segments

 
J.Martin
New Member

How to display/monitor application use of memory segments

Trying to confirm kernel parm settings are adequate for large application. I've displayed the settings for maxdsiz, maxssiz, maxtsiz and the 64bit parms using kctune.

How do I display what amount of each segment a process is using?
5 REPLIES 5
Bill Hassell
Honored Contributor

Re: How to display/monitor application use of memory segments

You'll need to install Glance Plus to see all these regions. You can get a bit of information from chatr and other development tools. However, the kernel limits you mentioned are per-process. Each process gets 4 quadrants of memory space to map as needed. The limits keep bad programs from using all of RAM. Of course, a correctly written program may need a lot of data space so you have to allow for this.


Bill Hassell, sysadmin
J.Martin
New Member

Re: How to display/monitor application use of memory segments

I have glance plus installed but don't see how to display the a particular process memory segment usage. I've tried both glance and gpm.

Is it possible to display a particular processes memory segment usage?

Thanks,

- joe
J.Martin
New Member

Re: How to display/monitor application use of memory segments

Hadn't seen the "M" option in Glance previously. Giving it a PID looks to display the information I am looking for.

Thanks for pointing me in the right direction.

- joe
Tim Nelson
Honored Contributor

Re: How to display/monitor application use of memory segments

There is also a great utility called kmeminfo ( non-supported HP tool ).

Do a search for it on this forum..

Per process mem usage etc...

Don Morris_1
Honored Contributor

Re: How to display/monitor application use of memory segments

In this case kmeminfo is the equivalent of hitting a fly with a sledgehammer -- effective, but a little much.

Glance is good too... but pstat's got enough information to handle this.

See attached program written with a different purpose in mind (summarizing Virtual/Physical/Lockable/Swap usage for a particular process or the system by memory object type). In this case, it could easily be modified to just print the virtual sizes for the 3 types you care about [PS_TEXT, PS_DATA, PS_STACK] for each PID on the system.