Sponsored Content
Full Discussion: Memory full
Operating Systems AIX Memory full Post 302625759 by zaxxon on Wednesday 18th of April 2012 08:54:12 AM
Old 04-18-2012
I have put your posting into code tags - there is a link how to use them.

To your question:

AIX as well as other UNIX derivates and Linux distributions uses a part of it's RAM as file cache. So it is absolutely normal to have a close to 100% usage of RAM.

What would be a problem is when your box starts to page.
From your posting you can see, that a part of your Paging Space is being used:
Code:
            size         inuse
            ...          ...
pg space    1572864      420673

So for some reason the OS had the need to page out some memory pages to disk as there was a demand for free RAM.
When this happens, you can monitor this by using things like
Code:
vmstat -tw 2 10

for example. There are two columns called pi and po, which stand for pages being paged out to disk and pages being paged in from disk which is somewhat slow in case they are needed again to be loaded into RAM (pi).
If there is any other values but 0, then you know that your box is paging. Even low values can sometimes mean problems on a busy system, as said especially when being paged in.
For long time monitoring it might be a good idea to use nmon which can be downloaded from IBM for free as it didn't come out of the box with AIX 5.3. There is also additional tools (nmon2rrd I think) to create graphs from the data to see at what time which impact happened.

As your AIX 5.3 might not be tuned, it could also be interessting what output the following command produces:
Code:
vmo -o maxclient% -o maxperm% -o minperm% -o lru_file_repage

You can also have a look at this:
https://www.ibm.com/developerworks/w....pdf?version=2
This User Gave Thanks to zaxxon For This Post:
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Memory full (waiting)

Hi When I launch topas I have this result I have a memory problem. I don't know how see the process which waiting. How can I do that? Thanks all!!! (0 Replies)
Discussion started by: Castelior
0 Replies

2. Shell Programming and Scripting

memory full warning message

Hi I wrote a script #!/usr/bin/ksh #set -x for fs in `df -k|awk '{print $1}'|sed -n "3,14 p"` do x=`df -kl | grep $fs | awk '{ print $5 }'` y=50% if then message="File System `df -k |grep $fs |awk '{print $6\", \"$5}'`... (1 Reply)
Discussion started by: namishtiwari
1 Replies

3. Linux

my box can't see full memory

Hi I'be recently installed Virtouzzo on Centos 5 on 16GB box , but the system could only see 4 GB of RAM, I installed the package kernel-PAE, but the virtuozzo kernel still can't see the full memory. even the kernel system can see 16GB of RAM is there any idea bout that ? Thanks (2 Replies)
Discussion started by: Raied
2 Replies

4. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

5. Programming

How to deal with lots of data in memory in order not to run out of memory

Hi, I'm trying to learn how to manage memory when I have to deal with lots of data. Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 Replies

6. Solaris

restrcit physical memory with zone.max-locked-memory

Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies

7. Shell Programming and Scripting

How to extract strings from full path when full path is not fixed

/Path/snowbird9/nrfCompMgrRave1230100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird6/nrfCompMgrRave1220100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird14/nrfCompMgrRave920100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.... (0 Replies)
Discussion started by: Shirisha
0 Replies

8. Solaris

[DOUBT] Memory high in idle process on Solaris 10 (Memory Utilization > 90%)

Hi Experts, Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing. Why memory utilization on solaris always looks high? I have statement about memory on solaris, is this true: Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies

9. AIX

100% Inode full with only 67% FS full.

AIX Version 6.1 and 7.1. I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device. It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
VMSTAT(1)						      General Commands Manual							 VMSTAT(1)

NAME
vmstat - report virtual memory statistics SYNOPSIS
vmstat [ -fsi ] [ drives ] [ interval [ count ] ] DESCRIPTION
Vmstat delves into the system and normally reports certain statistics kept about process, virtual memory, disk, trap and cpu activity. If given a -f argument, it instead reports on the number of forks and vforks since system startup and the number of pages of virtual memory involved in each kind of fork. If given a -s argument, it instead prints the contents of the sum structure, giving the total number of several kinds of paging related events which have occurred since boot. If given a -i argument, it instead reports on the number of inter- rupts taken by each device since system startup. If none of these options are given, vmstat will report in the first line a summary of the virtual memory activity since the system has been booted. If interval is specified, then successive lines are summaries over the last interval seconds. ``vmstat 5'' will print what the system is doing every five seconds; this is a good choice of printing interval since this is how often some of the statistics are sampled in the system; others vary every second, running the output for a while will make it apparent which are recomputed every second. If a count is given, the statistics are repeated count times. The format fields are: Procs: information about numbers of processes in various states. r in run queue b blocked for resources (i/o, paging, etc.) w runnable or short sleeper (< 20 secs) but swapped Memory: information about the usage of virtual and real memory. Virtual pages are considered active if they belong to processes which are running or have run in the last 20 seconds. A ``page'' here is 1024 bytes. avm active virtual pages fre size of the free list Page: information about page faults and paging activity. These are averaged each five seconds, and given in units per second. re page reclaims (simulating reference bits) at pages attached (found in free list) pi pages paged in po pages paged out fr pages freed per second de anticipated short term memory shortfall sr pages scanned by clock algorithm, per-second up/hp/rk/ra: Disk operations per second (this field is system dependent). Typically paging will be split across several of the available drives. The number under each of these is the unit number. Faults: trap/interrupt rate averages per second over last 5 seconds. in (non clock) device interrupts per second sy system calls per second cs cpu context switch rate (switches/sec) Cpu: breakdown of percentage usage of CPU time us user time for normal and low priority processes sy system time id cpu idle If more than 4 disk drives are configured in the system, vmstat displays only the first 4 drives, with priority given to Massbus disk drives (i.e. if both Unibus and Massbus drives are present and the total number of drives exceeds 4, then some number of Unibus drives will not be displayed in favor of the Massbus drives). To force vmstat to display specific drives, their names may be supplied on the command line. FILES
/dev/kmem, /vmunix SEE ALSO
systat(1), iostat(1) The sections starting with ``Interpreting system activity'' in Installing and Operating 4.2bsd. 4th Berkeley Distribution March 15, 1986 VMSTAT(1)
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy