Hi,
I am having memory problem. Whenever i run the Tivoli backup command from CLI "dsmc" my memory use is very high.
Topas shows the following output
Memory
Real, MB 35584
%Comp 17
%Noncomp 80.1
%Client 80.1
and "svmon" shows
Paging space has not been used
size inuse free pin virtual
memory 9109504 8979484 199652 643070 2828204
even after the command is finished the memory is not flushed. If i restart the machine memory use comes to normal and after the using "dsmc" problem comes again
when the command is running
svmin -P <PID of dsmc>
shows huge amount of memory use
but when the process is finished no more process remains
ps -ef | grep dsmc doesnot show any process
but the memory is not flushed
Use CODE-tags when posting code, data or logs for better readability and to keep formatting like indention etc., ty.
Having used up so much memory is totally normal on AIX since AIX uses the free RAM to cache files so it has not to read the files from "slow" physical disks again in case they will be needed.
Also you see that the ratio of your
is quite good. Comp is Computational Memory which is processes, ie. running programs etc. using memory. Noncomp (&Client) or Noncomputational Memory is usually cached files which can be flushed ie. cleaned up by LRUD if not used.
Other terms for them are Working Segments and Persistent Segments. Working is the programs etc. in memory, persistent are files on/from disks etc.
To see if you really have a problem on your box I'd recommend that you might fire off a
vmstat 1 10
at your peak times when you assume there is lot's of traffic.
As a start and regarding memory you might want to check the columns for pi and po. Or just post it here so we can see it.
If you have restarted the system AIX doesn't even have something to cache which would make sense, why it isn't using the memory even as filecache. When running a backup job with ADSM you shove a lot of disk data through memory and now the kernel has at least *something* to put into filecache - therefore it remains there until changes in your file utilization come up (via usage of different files, etc.). This is the reason the non-comp memory never goes back to 0%.
From what can be seen the system has absolutely nothing to do: The "r" and "b" columns (running and blocked kernel threads) are constantly 0, so there are no active processes in the moment.
Also the "sy", "us" and "wa" columns at the end are at 0, so there is no SYstem or USer process running and no process is WAiting for data. These are percentage values of the systems processing power and - together with "id" (idle) they (roughly) add up to 100. "id" is constantly at 99, which underlines this.
In the middle section the "pi" and "po" columns (page in and page out) are constantly zero so there is no paging activity going on. Tuning only has to take place when these values are non-zero with regularity, an occasional paging doesn't adversely affect the systems performance.
Another indication is that the "avm" (AVailable Memory) and "fre" (FREe memory) shows constant values. This means that nothing is claiming memory from the system, otherwise the numbers would change. At the end of the sampling interval you can see one single process being started (r=1) and subsequently some negligible amount of memory (2 pages ^= 8k) is claimed. Would there be sizeable activity these changes would be a lot bigger.
Bottom line: at the moment of the snapshot the only thing this system was doing was turning electric currency into heat.