fr and sr (from vmstat output) values are very high
Hi AIX Expert,
the fr (page freed/page replacement) and sr (pages scanned by page-replacement algorithm) values from the vmstat output (see below please) are very high. I usually see this high value during the oracle database backup. In addition, the page scan/page steal/ page faults values also very high..
Is this meaning that the server memory is maxed out?
Is there any tuning opportunity that we need to do?
Any advise is greatly appreciated. Thanks!
to File System 0.0 2558.5 Page Scans 1251.0 Page Steals 1219. Page Faults 756.0
Moderator's Comments:
edit by bakunin: Please use CODE-tags when posting code or terminal output to enhance readability. Thank you.
How do you reset the values that vmstat displays?
Vmstat displays a running average from the last the system was restarted on the first line, how do you reset these values without restarting the system? (Solaris 8) (3 Replies)
i have 2 question about vmstat
1)
pin (pagein) output of vmstat is always zero for our system
what is the meaning of this?
(pout significantly changes depending on the running processes)
2)
sometimes react output
of vmstat is given in K like 44K
sometimes it is given without any unit... (1 Reply)
Hello all
This is a sample vmstat output ...
$ vmstat 2 2
kthr memory page disk faults cpu
r b w swap free re mf pi po fr de sr hx hx hx hx in sy cs us sy id
1 0 0 23105784 7810488 323 767 1742 5 5 0 0 0 0 0 0 683 780 457 43 ... (9 Replies)
Hello,
I'm seeing this problem with vmstat, where the first line of output always has the same CPU statistics. For example:
neked@nekedmachine:~$ date && vmstat
Fri Jul 24 06:57:08 EDT 2009
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
r b swpd ... (0 Replies)
Hello everybody, When i run Nmon the output is really incomprehensible
vmstat 5
System configuration: lcpu=16 mem=24576MB ent=4.00
kthr memory page faults cpu
----- ----------- ------------------------ ------------ -----------------------... (3 Replies)
Hi all.
I need some assistance with my vmstat output.
We have several oracle db's running on our solaris machine:
SunOS rcworaprd 5.9 Generic_112233-07 sun4u sparc SUNW,Sun-Fire-480R
Recently I bumped up our main Oracle database to use 6 GB instead of 4 GB as vmstat output was showing... (1 Reply)
Hi all,
Recently I facing problem with my AIX server. we experience slowness on performance. there are some application installed in this server such as : Oracle 10g database, control-m client agent, and some monitoring tools.
when we're facing the problem we're noticing that vmstat value a... (7 Replies)
Hi,
Users are reporting performance issue on my Sun Solaris 10 server. I am on the server. I don't see a issue or I might be looking at the wrong thing. Please help.
I don't see anything on sar. it's all zero on that. Not sure why users are reporting high CPU and unresponsive at times. ... (1 Reply)
Hi,
Recently from the vmstat output in the image attached, the first line of the cpu idle column shows a value of 15. Although the subsequent values show higher than 90, is there a reason why the first value is so low?
Is this a problem?
Thanks. (4 Replies)
Discussion started by: anaigini45
4 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)