VMSTAT(1) — Unix Programmer’s Manual
NAME
vmstat − report virtual memory statistics
SYNOPSIS
vmstat [ −fs ] [ 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 none of these options are given, vmstat will report in a (usually) iterative fashion on the virtual memory activity in the system. In this case, the optional interval argument causes vmstat to report once each 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.
rin run queue
bblocked for resources (i/o, paging, etc.)
wrunnable 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.
avmactive virtual pages
fresize of the free list
Page: information about page faults and paging activity. These are averaged each five seconds, and given in units per second.
repage reclaims (simulating reference bits)
pipages paged in
popages paged out
frpages freed per second
deanticipated short term memory shortfall
srpages scanned by clock algorithm, per-second
up/hp/rk: 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
sysystem calls per second
cscpu context switch rate (switches/sec)
Cpu: breakdown of percentage usage of CPU time
ususer time for normal and low priority processes
sysystem time
idcpu idle
FILES
/dev/kmem, /vmunix
SEE ALSO
The sections starting with “Interpreting system activity” in Setting up 4.1bsd by W. Joy.
AUTHORS
William Joy and Ozalp Babaoglu
BUGS
There should be a screen oriented program which combines vmstat and ps(1) in real time as well as reporting on other system activity.
th Berkeley Distribution — 4/26/81