Sponsored Content
Operating Systems AIX AIX understanding memory using Post 303037086 by bakunin on Tuesday 23rd of July 2019 05:23:40 AM
Old 07-23-2019
Quote:
Originally Posted by Phat
I would like to understand better in AIX memory use
Basically you have three types of memory in an AIX system: "used" and "unused" and the "used" category divides into two parts: "computational" and "file" memory.

"unused" is memory the kernel has absolutely no use for. In a longer running (and correctly tuned) system this is near to zero.

"computational" memory is the memory used by loaded and running programs.

"file" memory is basically cache. All the memory not used for programs (but not strictly set aside by tuning provisions) is added to the file cache - over time. The kernel will only make use of memory to cache file access if it has an idea what to cache. This is why freshly started systems have lots of free memory. The kernel simply doesn't know what to put into the cache and therefore doesn't allocate a lot of it.

Should RAM become used over time and more computational memory is needed (i.e. more programs are started) the file cache is diminished accordingly or regrown again should memory become free again. The tuning parameters "numperm", "minperm", "maxperm", "minclient" and "maxclient" deal with how and when exactly file memory is turned into computational memory and vice versa. There is a daemon - the "least recently used daemon" or "lrud" for short - which constantly scans memory pages and decides when they should be claimed as "computational" or "file". What it is doing exactly shows in the output of vmstat -vs, i.e. "revolutions of the clock hand" means: since the last start the lrud has scanned the whole memory that often completely. If this value is fast growing you know that even if memory is not scarce right now it is at the brink of being exhausted and paging will start soon if any more memory is needed.

You may want to consult my "Most Incomplete Guide to Performance Tuning" for a more thorough (though not complete - this is a complex area) discussion about memory management in UNIX systems in general and how to assess it.

I hope this helps.

bakunin
These 5 Users Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

checking memory in AIX

I am using AIX 5.5 I have researched your site and found a few commands to try to check how much physical memory I have but the ones I found are not working. I was wondering does my system have a different command? I also checked the MAN pages could not find it there. Could somebody help? I... (2 Replies)
Discussion started by: rocker40
2 Replies

2. UNIX for Dummies Questions & Answers

understanding basic of storage in aix

Hi Can some one help to understand the follwoing thing: what is a simple mounting? for examle what the following lines says /dev/hd2 /usr/xxx if I have to install a software in a remote server, how i can use local cdrom to read the installation files from? what about... (3 Replies)
Discussion started by: ajaya
3 Replies

3. UNIX for Advanced & Expert Users

memory size under AIX

Hi, how to know size of physical memory under AIX ? Many thanks. PS : man -k memory man : 0703-310 Fichier man introuvable. uname -a AIX server1 1 5 005202DF4C00 (3 Replies)
Discussion started by: big123456
3 Replies

4. AIX

AIX Memory used by an Application

Hi, Is there any way to find the Memory allocated to an Application in AIX server (2 Replies)
Discussion started by: tinivt
2 Replies

5. UNIX for Advanced & Expert Users

HP vs AIX Memory

I have 2 boxes one running AIX 5.3 and the other running HP 11.31. Both systems have the same application running but HP seems to be using more memory than AIX by almost double. I have to use 2 different methods because both machines have different backend software to look at memory. What is the... (2 Replies)
Discussion started by: kfdalton
2 Replies

6. UNIX for Dummies Questions & Answers

Help in understanding AIX

Dear ALL, Where can I get the following information? what will happen exactly when i hit CTRL+C, CTRL+Z, CTRL+X, CTRL+D etc when the AIX terminal hangs...? The reason why I am asking this question is when ever I type a command at the terminal (say "select * from tab" or any command) the... (1 Reply)
Discussion started by: tenderfoot
1 Replies

7. Solaris

Understanding memory config with prtdiag -v

Hi. I have 2 SunFire V490 servers running Solaris 10. We may have to upgrade with more memory on one of them to make it compatible with the other. Here's the one with 12GB of RAM: Memory size: 12288 Megabytes ========================= CPUs =============================================== ... (1 Reply)
Discussion started by: th1amigo
1 Replies

8. UNIX for Advanced & Expert Users

Help understanding differences between AIX and RHEL

I have started a new job which requires AIX admin skills, which I have, and RHEL skills. Does anyone have a cheat sheet that if I know how to solve the problem in AIX how would I do that in RHEL? I was an IBM pre-sales technical trying to keep sales guys honest - not possible. Any other links to... (5 Replies)
Discussion started by: SpenceSnyder
5 Replies

9. AIX

AIX 6.1 memory tuning

Greetings, i'm wondering if there is a way to determine minimum memory requirement for AIX kernel and OS functions? We use memdetails script from perfpmr package to see actual memory allocation, for example like this: ===========================================================================... (5 Replies)
Discussion started by: dzodzo
5 Replies

10. AIX

AIX 6.1 error out of memory

i am facing issue in AIX 6.1 when i was running below command i face issued as show attached screenshot cat /audit/bin1 /audit/bin2 /audit/trail | auditpr -t 0 -v -h l,r,R,t,c,p,P |\ awk '/\s*audit object write event detected/ {print ll $6} { ll = $0}' Please use code tags next time... (1 Reply)
Discussion started by: aforabad
1 Replies
PAE(4)							 BSD/i386 Kernel Interfaces Manual						    PAE(4)

NAME
PAE -- Physical Address Extensions SYNOPSIS
options PAE DESCRIPTION
The PAE option provides support for the physical address extensions capability of the Intel Pentium Pro and above CPUs, and allows for up to 64 gigabytes of memory to be used in systems capable of supporting it. With the PAE option, memory above 4 gigabytes is simply added to the general page pool. The system makes no distinction between memory above or below 4 gigabytes, and no specific facility is provided for a process or the kernel to access more memory than they would otherwise be able to access, through a sliding window or otherwise. SEE ALSO
smp(4), tuning(7), config(8), bus_dma(9) HISTORY
The PAE option first appeared in FreeBSD 4.9 and FreeBSD 5.1. AUTHORS
Jake Burkholder <jake@FreeBSD.org> BUGS
Since KLD modules are not compiled with the same options headers that the kernel is compiled with, they must not be loaded into a kernel com- piled with the PAE option. Many devices or their device drivers are not capable of direct memory access to physical addresses above 4 gigabytes. In order to make use of direct memory access IO in a system with more than 4 gigabytes of memory when the PAE option is used, these drivers must use a facility for remapping or substituting physical memory which is not accessible to the device. One such facility is provided by the busdma interface. Device drivers which do not account for such devices will not work reliably in a system with more than 4 gigabytes of memory when the PAE option is used, and may cause data corruption. The PAE kernel configuration file includes the PAE option, and explicitly excludes all device drivers which are known to not work or have not been tested in a system with the PAE option and more than 4 gigabytes of memory. Many parameters which determine how memory is used in the kernel are based on the amount of physical memory. The formulas used to determine the values of these parameters for specific memory configurations may not take into account the fact there may be more than 4 gigabytes of memory, and may not scale well to these memory configurations. In particular, it may be necessary to increase the amount of virtual address space available to the kernel, or to reduce the amount of a specific resource that is heavily used, in order to avoid running out of virtual address space. The KVA_PAGES option may be used to increase the kernel virtual address space, and the kern.maxvnodes sysctl(8) may be used to decrease the number of vnodes allowed, an example of a resource that the kernel is likely to overallocate in large memory configurations. For optimal performance and stability it may be necessary to consult the tuning(7) manual page, and make adjustments to the parameters docu- mented there. BSD
April 8, 2003 BSD
All times are GMT -4. The time now is 02:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy