Sponsored Content
Top Forums UNIX for Advanced & Expert Users j2_maxPageReadAhead & j2_nBufferPerPagerDevice and CIO Post 302232720 by zaxxon on Friday 5th of September 2008 04:00:48 AM
Old 09-05-2008
When I type "vmstat -vs" on any AIX 5.3 machine, I get:

Code:
root@somebox:/> vmstat -vs
           1743435524 total address trans. faults
            400484880 page ins
             66634052 page outs
                    0 paging space page ins
                    0 paging space page outs
                    0 total reclaims
            896069655 zero filled pages faults
             79684162 executable filled pages faults
            969679308 pages examined by clock
                 1453 revolutions of the clock hand
            379300865 pages freed by the clock
             12301371 backtracks
                    0 free frame waits
                    0 extend XPT waits
              9308168 pending I/O waits
            459670082 start I/Os
             32358220 iodones
           1045168868 cpu context switches
            192183708 device interrupts
            106783424 software interrupts
            580781613 decrementer interrupts
               266715 mpc-sent interrupts
               215160 mpc-receive interrupts
            136135094 phantom interrupts
                    0 traps
           9578158818 syscalls
              4259840 memory pages
              4002637 lruable pages
               308553 free pages
                    6 memory pools
               569732 pinned pages
                 80.0 maxpin percentage
                  5.0 minperm percentage
                 80.0 maxperm percentage
                 64.4 numperm percentage
              2579734 file pages
                  0.0 compressed percentage
                    0 compressed pages
                 64.4 numclient percentage
                 80.0 maxclient percentage
              2579734 client pages
                    0 remote pageouts scheduled
                   28 pending disk I/Os blocked with no pbuf
                    0 paging space I/Os blocked with no psbuf
                 2484 filesystem I/Os blocked with no fsbuf
                  585 client filesystem I/Os blocked with no fsbuf
                 3554 external pager filesystem I/Os blocked with no fsbuf
                    0 Virtualized Partition Memory Page Faults
                 0.00 Time resolving virtualized partition memory page faults

So either you still did not enter that command or your vmstat is not recognizing parameters correct, which I doubt.
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

turning CIO on and how to monitor

Hi Guys, I have a database server where we run AIX 5.3 on a power5 box and we just turned on CIO (concurrent I/O) for the database filesystems. Now my assumption is that enabling CIO the database basically will bypass the filesystem cache releasing some extra memory that can be allocated... (1 Reply)
Discussion started by: hariza
1 Replies

2. AIX

turning CIO on and how to monitor

Hi Guys, I have a database server where we run AIX 5.3 on a power5 box and we just turned on CIO (concurrent I/O) for the database filesystems. Now my assumption is that enabling CIO the database basically will bypass the filesystem cache releasing some extra memory that can be allocated... (1 Reply)
Discussion started by: hariza
1 Replies

3. Linux

Is Concurrent I/O (CIO) available on Linux?

Hi Guys, I just wondering if any of the AIX gurus with some exposure to Linux Redhat can tell me whether in Linux ( Red Hat or OpenSuse ) we have a similar option/capability like the CIO (Concurrent I/O) which is currently available on AIX. The reason I'm asking is because in the past we... (2 Replies)
Discussion started by: arizah
2 Replies

4. UNIX for Advanced & Expert Users

CIO in AIX

Hi, I'm reading AIX documentation : Examples 1.To list the mounted file systems, enter: mountThis command produces output similar to the following: node mounted mounted over vfs date options ---- ------- ------------ --- ------------ ... (2 Replies)
Discussion started by: big123456
2 Replies
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)
All times are GMT -4. The time now is 11:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy