Sponsored Content
Full Discussion: output of vmstat
Top Forums UNIX for Advanced & Expert Users output of vmstat Post 302090073 by RTM on Friday 22nd of September 2006 09:54:21 AM
Old 09-22-2006
Quote:
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)
Page out is when the system dumps a page to disk that hasn't been accessed in the timeframe set up - meaning no one attempted to access that page (the data that was taken from disk and put into memory) AND someone has requested some other data to be read and the system needed to dump some of the data it had in memory for the new data being requested.

Page in is when someone DOES request the data that was accessed a while ago but had been paged out (the data was sent to disk). The system gets the data that was paged out (as long as it hasn't changed) and brings it back into memory. Having pagein at zero would be expected on a server.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

vmstat output with date & timestamp

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)
Discussion started by: luft
9 Replies

2. Shell Programming and Scripting

Capturing and sending of vmstat output everyday

I need to capture the vmstat output of a server every 5 minutes, in a text filename with the name in the format vmoutput. yesterday's date.txt. I need to get the vmstat o/p for the whole day with 5 minutes interval and send it (preferably ftp) to my local desktop folder. eg: vmstat 300... (1 Reply)
Discussion started by: yuvanash
1 Replies

3. UNIX for Advanced & Expert Users

vmstat's cpu stats on first line of output are always the same

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)
Discussion started by: neked
0 Replies

4. AIX

vmstat incomprehensible output

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)
Discussion started by: Vit0_Corleone
3 Replies

5. Solaris

help with vmstat output

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)
Discussion started by: jamie_collins
1 Replies

6. AIX

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... (7 Replies)
Discussion started by: Beginer0705
7 Replies

7. Solaris

Different VMSTAT output on Linux and Solaris machines

Hi, I am porting a piece of code from Solaris to Linux. Code uses VMSTAT command. On Solaris machine VMSTAT output is following: uname -a: SunOS rgsm01 5.9 Generic_118558-03 sun4u sparc SUNW,Sun-Fire-V440 vmstat: kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr m1 m2... (3 Replies)
Discussion started by: Basant Mishra
3 Replies

8. UNIX for Dummies Questions & Answers

Pls. help with vmstat output...

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)
Discussion started by: samnyc
1 Replies

9. Linux

Vmstat

I m checking idle time using vmstat, below are the results var=$(ssh wmtmgr@$hostname vmstat | tail -1 | awk '{print $15}') 89 and now im subtracting 89 with 100 & im getting expected results expr 100 - $var 11 Now How can I get the result 11 in one line code? (4 Replies)
Discussion started by: sam@sam
4 Replies

10. Solaris

Reason for abnormal value in vmstat output

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
PROCINFO-NG(8)							Linux System Manual						    PROCINFO-NG(8)

NAME
procinfo - display system statistics gathered from /proc SYNOPSIS
procinfo [ -fdDSbrhv ] [ -nN ] DESCRIPTION
procinfo gathers some system data from the /proc directory and prints it nicely formatted on the standard output device. The meanings of the fields are as follows: Memory: See the man page for free(1) Bootup: The time the system was booted. Load average: The average number of jobs running, followed by the number of runnable processes and the total number of processes, followed by the PID of the last process run. The pid of the last running process will probably always be procinfo's PID. user: The amount of time spent running jobs in user space. nice: The amount of time spent running niced jobs in user space. system: The amount of time spent running in kernel space. Note: the time spent servicing interrupts is not counted by the kernel (and noth- ing that procinfo can do about it). idle: The amount of time spent doing nothing. uptime: The time that the system has been up. The above four should more or less add up to this one. page in: The number of disk blocks paged into core from disk. 1 block is equal to 1 kiB. page out: The number of disk blocks paged out of core to disk. This includes regular disk-writes. swap in: The number of memory pages paged in from swap. swap out: The number of memory pages paged out to swap. context: The number of context switches, either since bootup or per interval. Disk stats(hda, hdb, sda, sdb): The number of reads and writes made to disks, whether CD-ROM, hard-drive, or USB. Shows all disks if they either are an hdX or sdX, or if they have a non-zero read/write count. Interrupts: Number of interrupts serviced since boot, or per interval, listed per IRQ. OPTIONS
-nN Pause N second between updates. This option implies -f. It may contain a decimal point. The default is 5 seconds. When run by root with a pause of 0 seconds, the program will run at the highest possible priority level. -d For memory, CPU times, paging, swapping, disk, context and interrupt stats, display values per second rather than totals. This option implies -f. -D Same as -d, except that memory stats are displayed as totals. -S When running with -d or -D, always show values per second, even when running with -n N with N greater than one second. -b Display numbers of bytes rather than number of I/O requests. -r This option adds an extra line to the memory info showing 'real' free memory, just as free(1) does. The numbers produced assume that Buffers and Cache are disposable. -H Displays memory stats in 'Human' (base 1024) numbers (KiB, MiB, GiB), instead of implied KBytes. -h Print a brief help message. -v Print version info. INTERACTIVE COMMANDS
When running procinfo fullscreen, you can change its behaviour by pressing d, D, S, r and b, which toggle the flags that correspond to their same-named commandline-options. In addition you can press q which quits the program. FILES
/proc The proc file system. BUGS
All of these statistics are taken verbatim from the kernel, without any scaling. Any case where the kernel specifies that a particular field means something different from how it is documented in this man-page, the kernel always wins. Some features of the original procinfo were elided, as they were considered non-useful, especially as many of them don't change anymore, and have better utilities for listing/displaying them. SEE ALSO
free(1), uptime(1), w(1), init(8), proc(5). AUTHOR
Adam Schrotenboer <adam@tabris.net> v2.0 2007-05-05 PROCINFO-NG(8)
All times are GMT -4. The time now is 01:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy