Production server is showing 98% memory utilization

[BW Moll]

What column do I look at in glance to tell me which process(es) are using the most memory

HP-UX 11.11

Thank you !!

[S.Rider · Accepted solution]

RSS = Real Memory
VSS = Virtual memory

[BW Moll]

Is there any way I can sort the glance view to show high RSS memory processes first?

Thank you !!

[Jeeshan]

Check in two way other than glance

1. Check dbc_max_pct.

2. export UNIX95=1;ps -ef -o comm,pcpu,vsz,args | grep

[Bill Hassell]

In Glance, just type the letter o, then return (or 1 then return). This will show you the interesting processes screen. Move the cursor down to the bottom of the list where it says to sort the list and type in rss then return. Say no to the question about making this the default. That way, the change goes away when you exit Glance. Then press the Perform Task softkey.

For a list of all the 1-letter commands, just type ? while running Glance.

[Bill Hassell]

In Glance, just type the letter o, then return (or 1 then return). This will show you the interesting processes screen. Move the cursor down to the bottom of the list where it says to sort the list and type in rss then return. Then press the Perform Task softkey.

For a list of all the 1-letter commands, just type ? while running Glance.

[Bill Hassell]

ahsan: To clarify just a bit:

> 1. Check dbc_max_pct.
>
> 2. export UNIX95=1;ps -ef -o comm,pcpu,vsz,args | grep

dbc_max_pct is a setting for swap space management and will not any provide any information about processes consuming large amounts of RAM.

It is always a bad idea to export UNIX95. UNIX95 changes the behavior of several libraries and processes. For ps, it is a good setting to use as it adds several new options. But when exported, every process you run from then on may be affected by this setting. For instance, Ignite may fail in many versions.

Instead, the command line should be:

UNIX95=1 ps -eo vsz,pid,ppid,pcpu,args | sort -rn

In this example, UNIX95=1 exists onlt for the duration of the ps command, and yes, it is OK to assign a variable in front of a command name. As mentioned in other threads, grep is a very bad tool for selecting processes because it is non-selective. That means that grep sh will find many, many unwanted processes. Instead, use the _C option in ps:

UNIX95=1 ps -fC sh

Compare the above results with:

ps -ef | grep sh

(not a very nice list at all)