Sponsored Content
Top Forums Shell Programming and Scripting Capturing computational/non computational memory from topas Post 302890096 by bakunin on Tuesday 25th of February 2014 07:17:27 AM
Old 02-25-2014
Quote:
Originally Posted by Nowshath
Topas is performance monitoring tool in AIX, so that i ask you how to capture the % Comp and % noncomp from topas command.
Yes, but "topas" is designed for interactive use only. If you want to skim the values from some output stream you should use "vmstat" rather than "topas" because "vmstat"s output is a character stream whereas "topas"s output is full of control characters necessary for the screen control.

First: what is computational and non-computational memory? Memory is allocated controlled by some "vmo" (see "man vmo") tunables: "minperm%", "maxperm%", "minclient", "maxclient", "lrud_file_repage", ... Basically the AIX kernel tries to put otherwise unused memory to some use dedicating some part (the tunables control how big this part is) of it to the file cache. "Computational memory" is the part of the memory in use given to running processes. "Non-Computational memory" is the memory used for file cache (and a few other buffers of minor significance). Together, computational and non-computational memory is "used memory".

"minperm%" and "maxperm%" control when and under which circumsteances non-computational memory is changed to computational memory and vice versa (which is done by the lrud-daemon), "numperm%" tells you, where - in between minperm and maxperm - you are right now.

After this rather lengthy explanations, here is a sample output of "vmstat -v" (AIX 7.1, idle system):

Code:
# vmstat -v 
             15073280 memory pages
             12080419 lruable pages
             13429620 free pages
                    3 memory pools
               850498 pinned pages
                 95.0 maxpin percentage
                  3.0 minperm percentage
                 90.0 maxperm percentage
                  4.4 numperm percentage
               536202 file pages
                  0.0 compressed percentage
                    0 compressed pages
                  4.4 numclient percentage
                 90.0 maxclient percentage
               536202 client pages
                    0 remote pageouts scheduled
                    5 pending disk I/Os blocked with no pbuf
                    0 paging space I/Os blocked with no psbuf
                 1972 filesystem I/Os blocked with no fsbuf
                    0 client filesystem I/Os blocked with no fsbuf
                    0 external pager filesystem I/Os blocked with no fsbuf
                  7.3 percentage of memory used for computational pages

I have marked the relevant lines bold: numperm percentage is the (%) amount of memory currently used by the file cache. Compare this to the number of totally allocated pages and you get the sizes of computational and non-computational memory. Note, that some numbers are percentages, some numbers are memory pages! Memory pages can be various sizes in AIX, but the most common are 4k. So, for instance, "2500" is roughly 10M.

I hope this helps.

bakunin
 

7 More Discussions You Might Find Interesting

1. AIX

Memory usage statistic? (topas, nmon)

hi, how can i diplay: - the ammount RAM used /free - ammount of ram used from a pid or prozess we have the problem, that malloc is returing a NULL pointer errno = 12 ( not enough space). but i think there is still ram free. nmon : shows all memory used ? Memory Use Physical Virtual... (7 Replies)
Discussion started by: Lazzar
7 Replies

2. UNIX for Advanced & Expert Users

Need Help installing a Computational Tool Kit

Hi ! I have been trying to install IMSL Computational Tool Kit on a server. It is a Lunix Redhat V.4 with Intel pentium d processor and Intel fortran compiler 8.1 and the type of command shell we run is bash. I dont know if the problem is with the Installation or the Lunix system. I have... (1 Reply)
Discussion started by: dsmv
1 Replies

3. Cybersecurity

Computational complexity

This is a general question about the practical use of computational complexity in security. Wikipedia has a good article about the theoretical background of computational complexity. In the course of conversation with colleagues, a topic that is brought up occassionally is the security of any... (2 Replies)
Discussion started by: gratuitous_arp
2 Replies

4. Emergency UNIX and Linux Support

Appending the contents of two files in computational manner

Hi, I have two files say file 1 file 2 File1 1 2 4 5 File 2 asdf adf How to get the ouput something like asdf1 adf1 asdf2 adf2 asdf4 adf4 asdf5 (5 Replies)
Discussion started by: ecearund
5 Replies

5. AIX

topas - computational memory 95% : Any Impact?

Hello Gurus, I am using AIX 5 and on running topas command. I can see the computational memory is 93.3% with Swap Paging memory at 2.2%. Could you please advise if there is any impact by the growth of computational memory? Below is the stat: MEMORY Real,MB 22528 % Comp 93.3 %... (12 Replies)
Discussion started by: panchpan
12 Replies

6. AIX

How to use topas to display its Memory section alone

Hi, I'm planning to write a script to monitor the memory utilization and so decided to use topas. i'm not familiar with this command Could anyone help me with an idea on how to display the Memory section alone in the topas... :) It will be very helpful if you could specify the command... (2 Replies)
Discussion started by: kaushik_87
2 Replies

7. Shell Programming and Scripting

Shell script for %computational memory & % non computational memory

Dear, How to calculate %computational memory and %non computational memory from AIX server. What command used to find out %computational memory and % non computational memory except topas. Regards Nowshath (1 Reply)
Discussion started by: Nowshath
1 Replies
lotsfree_pct(5) 						File Formats Manual						   lotsfree_pct(5)

NAME
lotsfree_pct - sets the upper bound before paging daemon starts stealing pages, specified as a percentage of available physical memory VALUES
Default Allowed values Must not be less than (see desfree_pct(5)). DESCRIPTION
is a tunable parameter to set the upper bound before the paging daemon starts stealing pages. It is specified as a percentage of physical memory available after boot. must be a positive integer between 0 and 30 and must be equal to or greater than is the lower bound before paging daemon starts stealing pages (see desfree_pct(5)). The paging daemon in HP-UX acts on a "two hand" model. The daemon runs at least once a second, with one part marking pages of virtual address space as "unused". If the page is referenced before this "aging" hand returns, it will be marked as "used" again. Another section of the daemon, the "steal" hand follows the age hand (the distance between them varies in a well bounded range) and processes pages which are still marked unused, since needed or frequently accessed pages would have a high likelihood of being referenced in the gap between the hands. Exactly how the steal hand treats the pages still marked as unused depends on the comparison of free system physical memory and three pag- ing parameters: and Between and is a periodically re-calculated and, hence, floating threshold known as Thus and are the upper and lower bounds between which moves. is an expression how much the system maintains, in percentage terms (percentage of physical memory available after boot). o If is greater than the system's memory availability is in good shape. The steal hand does nothing as a lot of memory is still available on the system, so there is no need to "steal" a page that might be needed soon. o In the more common case, when is lower than (but higher than the steal hand will begin to steal pages that have remained unreferenced from when the age hand last marked them. "Stealing" a page refers to the process of freeing the page from being allocated for a partic- ular virtual page and making it available for general allocation again. If falls below but still is more than memory availability is still in reasonable shape, but the paging daemon begins stealing pages more aggressively, including putting lower-priority processes to sleep to free up their memory. o When is less than memory availability is getting more critical; and the paging daemon begins deactivating low-priority processes, in other words, swapping out pages to the swap device. Since the exact memory topography varies widely across supported platforms, these three boundary values are tunable to allow for cases where the default values are insufficient, or where the system administrator requires more control over the actions of the paging daemon. In general, however, the automatic calculation performed by default should suffice for most systems. is a system calculated value. Who Is Expected to Change This Tunable? Anyone with super-user privileges. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? The tunable should only be raised if an administrator feels that the current value provides insufficient free physical memory required by a short lived but critical process. Increasing (and hence to an amout equal to or greater than the amount of physical memory required by this process allows the swapper to move out less frequently used pages from longer running programs, increasing the probability of having the desired amount of memory on hand without waiting for to drop below or during the execution of this critical process. Unless the current is set very low, raising for a process that is not short lived is fairly pointless as will almost certainly drop below and more likely even below thus waking up the swapper and allowing for the physical memory to be freed up over the longer running time as the process requires it. What are the Side Effects of Raising the Value? The swap daemon will begin to steal less-frequently accessed pages from running processes. If large amounts of physical memory is already available without the above situation, this will only slow the already running processes if they need to swap back in their stolen pages. Large amounts of free physical memory without short-lived processes that need it (as mentioned above) is simply a waste. When Should the Value of This Tunable Be Lowered? The tunable should be lowered on systems where swapping is occurring that still have more physical memory available than is needed on aver- age, and that have no sudden sharp peaks in memory usage. What are the Side Effects of Lowering the Value? System swap will occur at a lower memory level. If is set too low (keeping in mind that can never be greater than the system might stall due to memory starvation upon new allocation even though swap space is available. The stall would not be fatal, as the swap daemon run eventually, but will certainly hamper performance. What Other Tunable Values Should Be Changed at the Same Time? should be considered when modifying since Attempting to set above is meaningless and will result in an error. Notes Starting with HP-UX 11iv2, HP recommends the use of to specify the upper bound for the paging daemon. ERROR VALUES
Memory resource management infrastructure is busy. Please try later. Attempting to set above An invalid value is entered that is not an integer between 0 and 30, such as an negative number. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
desfree_pct(5). Tunable Kernel Parameters lotsfree_pct(5)
All times are GMT -4. The time now is 12:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy