08-13-2013
Thanks much for your response....@ Robin, @ Zaxxon...and @Michael
I really appreciate your ideas.......
As per your comments/ideas, i understand that
It is not a problem/bottleneck...If RAM (memory) utilization in AIX goes beyond 99% .
The only issue is when there is a paging activity......lets say....paging space goes above 20% (page in/out)
In my case, i see lot of Memory utilization 99% all the time
but 1% paging space.
no paging activity.
REAL MEMORY --> 24 GB
% comp --> 29
% non comp --> 64
% client --> 64
paging space
1 % used
Please correct me if i am wrong.
Last edited by System Admin 77; 08-13-2013 at 06:52 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I have a question, can you guys please help me by giving your valuable suggestons:
I am using AIX 5L, running oracle 7 version. I need to increase the oracle memory to 40 MB more. Currently Oracle occupies 260M. I wanted to know whether I can increase the memory without any problem.... (1 Reply)
Discussion started by: kollam68
1 Replies
2. AIX
Hi All,
I have a question, can you guys please help me by giving your valuable suggestons:
I am using AIX 5L, running oracle 7 version. I need to increase the oracle memory to 40 MB more. Currently Oracle occupies 260M. I wanted to know whether I can increase the memory without any problem.... (3 Replies)
Discussion started by: kollam68
3 Replies
3. AIX
Hi,
We have AIX 5.1 machine of RAM 8 GB and paging space is 8GB. we are getting high memory usage of almost 99%.Can anybody please help in this ?
Partial vmstat o/p
kthr memory
----- -----------
r b avm fre
2 1 278727 1143
There is no paging issue.Becoz in... (5 Replies)
Discussion started by: jayakumarrt
5 Replies
4. AIX
How to check the memory usage on AIX by various processes? (1 Reply)
Discussion started by: aajmani
1 Replies
5. HP-UX
how can I find cpu usage memory usage swap usage and
I want to know CPU usage above X% and contiue Y times and memory usage above X % and contiue Y times
my final destination is monitor process
logical volume usage above X % and number of Logical voluage above
can I not to... (3 Replies)
Discussion started by: alert0919
3 Replies
6. AIX
How to monitor the IBM AIX server for I/O usage, memory usage, CPU usage, network usage, storage usage? (3 Replies)
Discussion started by: laknar
3 Replies
7. AIX
Hi,
I have AIX 5.3TL8 two node cluster using HACMP and have 10g database using RAW devices. I am seeing gradual increase in comp% memory everyday and it reaches 100% and evicts the node, we had 4 evictions in 40days.
I am pasting vmstat and vmo output, anyone seen this issue?
... (5 Replies)
Discussion started by: navin7386
5 Replies
8. AIX
hi,
I want to ask , my AIX 6.1 is always used about 97% memory.
Is this normal ?
or any command can free up memory like Linux ?
thanks. (1 Reply)
Discussion started by: virusxx
1 Replies
9. AIX
Hello,
Am working on small program that used to calculate the memory usage of AIX servers. Am using svmon -G command to get the memory usage. For example, consider the following output.
$ svmon -G
size inuse free pin virtual mmode
memory ... (9 Replies)
Discussion started by: maruthu
9 Replies
10. AIX
Hi, i have 2 identical web servers using AIX. I use nmon analyser to check their performance.
The server A exceeds 20% memory usage for system, 5% for cache and the rest 75% for processes. While, it uses 4% of Paging Space.
The server B exceeds 20% for system, 45% for cache and 35% for processes.... (24 Replies)
Discussion started by: dim
24 Replies
MLOCK(2) Linux Programmer's Manual MLOCK(2)
NAME
mlock - disable paging for some parts of memory
SYNOPSIS
#include <sys/mman.h>
int mlock(const void *addr, size_t len);
DESCRIPTION
mlock disables paging for the memory in the range starting at addr with length len bytes. All pages which contain a part of the specified
memory range are guaranteed be resident in RAM when the mlock system call returns successfully and they are guaranteed to stay in RAM until
the pages are unlocked by munlock or munlockall, until the pages are unmapped via munmap, or until the process terminates or starts another
program with exec. Child processes do not inherit page locks across a fork.
Memory locking has two main applications: real-time algorithms and high-security data processing. Real-time applications require determin-
istic timing, and, like scheduling, paging is one major cause of unexpected program execution delays. Real-time applications will usually
also switch to a real-time scheduler with sched_setscheduler. Cryptographic security software often handles critical bytes like passwords
or secret keys as data structures. As a result of paging, these secrets could be transfered onto a persistent swap store medium, where they
might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated.
Memory locks do not stack, i.e., pages which have been locked several times by calls to mlock or mlockall will be unlocked by a single call
to munlock for the corresponding range or by munlockall. Pages which are mapped to several locations or by several processes stay locked
into RAM as long as they are locked at least at one location or by at least one process.
On POSIX systems on which mlock and munlock are available, _POSIX_MEMLOCK_RANGE is defined in <unistd.h> and the value PAGESIZE from <lim-
its.h> indicates the number of bytes per page.
NOTES
With the Linux system call, addr is automatically rounded down to the nearest page boundary. However, POSIX 1003.1-2001 allows an imple-
mentation to require that addr is page aligned, so portable applications should ensure this.
RETURN VALUE
On success, mlock returns zero. On error, -1 is returned, errno is set appropriately, and no changes are made to any locks in the address
space of the process.
ERRORS
ENOMEM Some of the specified address range does not correspond to mapped pages in the address space of the process or the process tried to
exceed the maximum number of allowed locked pages.
EPERM The calling process does not have appropriate privileges. Only root processes are allowed to lock pages.
EINVAL len was not a positive number.
CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code.
SEE ALSO
mlockall(2), munlock(2), munlockall(2), munmap(2), setrlimit(2)
Linux 1.3.43 1995-11-26 MLOCK(2)