Rushank,
The memory line in the output from 'swapinfo -ta' is about pseudo-swap. You turn pseudo-swap on by setting the kernel parameter swapmem_on=1.
You can turn pseudo-swap off by setting swapmem_on=0.
In your case, pseudo-swap is at 41% utilization, which is ok. However, if this value gets close to 100%, you should be concerned. Should that happen, and if you have plenty of disk space, just disable pseudo-swap and enable more device swap. Indeed, we have had problems with Sybase using up pseudo-swap. The recommendation from both HP and Sybase was to disable pseudo-swap. HP recommended the same for Oracle database.
The Glance adviser syntax /opt/perf/examples/proc_mem_leak is designed for detecting memory leaks. It won't detect memory bottlenecks.
If you want to monitor a specific process, you can create your own adviser syntax and run it as mentioned before (use PROCESS LOOP) See /opt/perf/paperdocs/gp/C/adviser.pdf for more examples and details.
It seems to me that you should increase nfile. I would double it, at least.
The nbuf is a bit confising because you have configured dynamic buffer cache. It shouldn't be a concern. The only thing I would change is dbc_max_pct and dbc_min_pct. With dbc_max_pct equal to 8, you buffer cache may grow up to 8% of your physical memory. So, if you have 8Gb, your buffer cache may grow up to 640 Mb. HP recommends that you don't need more than about 300 Mb of buffer cache. Ultimately, you want to monitor GBL_MEM_CACHE_HIT_PCT
in Glance. If you lower dbc_max_pct and this metric is at least 80-90% on average,
it is ok. The moment GBL_MEM_CACHE_HIT_PCT starts show significat decrease, you should then increase dbc_max_pct. But the way things look right now, it is too high.
Here is some info on Buffer Headers (from /opt/perf/paperdocs/gp/C/metrics.txt):
TBL_BUFFER_HEADER_AVAIL
--------------------
The configured number of headers pointing to buffers in the file
system buffer cache. This can be set by the nbuf kernel
configuration parameter. nbuf is used to determine the maximum
total number of buffers on the system.
These are used to manage the buffer cache, which is used for all
block IO operations. When nbuf is zero, this value depends on
the bufpages size of memory (see System Administration Tasks
manual). A value of "na" indicates either a dynamic buffer cache
configuration, or the nbuf kernel parameter has been left
unconfigured and allowed to float with the bufpages parameter.
This is not a maximum available value in a fixed buffer cache
configuration. Instead, it is the initial configured value. The
actual number of used buffer headers can grow beyond this initial
value.
TBL_BUFFER_HEADER_USED
--------------------
The number of buffer headers currently in use.
This dynamic value will rarely change once the system boots.
During the system bootup, the kernel allocates a large number of
buffer headers and the count is likely to stay at that value
after the bootup completes. If the value increases beyond the
initial boot value, it will not decrease. Buffer headers are
allocated in kernel memory, not user memory, and therefore, will
not decrease.
This value can exceed the available or configured number of
buffer headers in a fixed buffer cache configuration.
This metric is updated every 30 seconds or the sampling interval,
whichever is greater.
