It looks like when I list top proecesses on nmon, no single process ever takes more than 1% of the memory. Even then, only one or two processes use use 1% at once. The utilization report that uses nmon says that there is 2.6 GB of 40GB Available. It sounds like that nmon AIX "sees" the memory but the application os is actually not using all of it.
If you are intrested attached is some output from nmon.
The m option seemns to be reporting differently than the t option.
I don't plan to change paging because no paging is taking place and it will take alot of my disk space to build paging at 80GB.
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)
Hi
i am new to aix , we are using aix 5.3 version and model is 510 and 520 model servers. in our servers contains 8 gb ram.
but servers average ram usage is reaching 99.9% , can any body help on this , is any impact if memory usage reach 99.9%.
Regards
Balaji Poola (2 Replies)
I have the following program:
int main(int argc, char** argv){
unsigned long int mean=0;
for(int i=1;i<10;i++){
mean+=poisson(12);
cout<<mean<<endl;
}
cout<<"Sum of poisson: "<< mean;
return 0;
}
when I run it, I get the... (4 Replies)
It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very... (6 Replies)
Hello together,
i have a strange memory behavior on a AIX 7.1 System, which i cannot explain.
The Filesystem-Cache will not be grow up and drops often after few minutes. I know if a file was deleted, that the same segment in the FS-Cache will also be cleared. But i am not sure if this is the... (8 Replies)
I am not sure what is wrong, but I have some strange behavior when printing things out.
I do create a file with only one word test, no space, no new line etc.
nano file<enter>
test<ctrl x>y<enter>
Server 1 gets (fail)
awk '{print "+"$0"*"}' file
*test
Server 2 gets (OK)
awk '{print... (9 Replies)
I am trying to create an archive using tar. I am specifying a list of directories using the -L option. For testing purposes I created a simple directory structure:
/backup/test
/backup/test/test1
/backup/test/test2
The file specified by the -L option, named files.txt, contains:... (8 Replies)
Hi All,
I am facing a strange problem while grepping for a process. Here is the small script that i have written.
It will look for any process running with the parameter passed to the script.
If no process is running it should print appropriate message.
$ cat t.ksh
#!/bin/ksh
set -x
... (9 Replies)
Hello All,
I have a strange issue. I've created a shell script which connects to RMAN (Oracle Recovery Manager) and executes full DB backup. I then executed this script with nohup and in the background:
$ nohup my_script.sh > logfile.log 2>&1 &The issue is that when I tried to take a look into... (6 Replies)
Discussion started by: JackK
6 Replies
LEARN ABOUT BSD
vmstat
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)