Skip to main content

Vmstat Output explained



vmstat :

vmstat is a tool in Unix/Linux which is used to Report virtual memory statistics. It shows how much virtual memory there is, how much is free and paging activity. Most important, you can observe page-ins and page-outs as they happen.
 
vmstat  reports  information about processes, memory, paging, block IO, traps, and cpu activity.
 
> vmstat
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu-----
 r  b   swpd   free   buff  cache        si   so    bi    bo   in   cs us sy id wa st
 0  0  21688 12797396 850716 15372668    0    0     3    35    0    0  1  0 99  0  0
 0  0  21688 12789292 850716 15372668    0    0     0  1355  883  744  1  0 99  0  0
 1  0  21688 12784648 850716 15372676    0    0     0    15 1934 1292  6  0 93  0  0
 2  0  21688 12781356 850716 15372736    0    0     0    16 2222 2094  8  1 92  0  0
 0  0  21688 12809992 850716 15376880    0    0     0    16 1959 1621  6  1 93  0  0
 1  0  21688 12809992 850716 15376888    0    0     0    29 1090  860  1  0 99  0  0
 0  0  21688 12808936 850716 15376888    0    0     0   132  931  798  1  0 99  0  0
 0  0  21688 12809496 850716 15376888    0    0     0     5  868  768  1  0 99  0  0
 1  0  21688 12793492 850716 15376888    0    0     0     5 1701 1177  5  0 95  0  0
 1  0  21688 12767728 850716 15376928    0    0     0  1355 8553 2589 48  1 51  0  0
13  0  21688 12765680 850716 15376968    0    0     0    24 7619 3122 44  1 56  0  0
 
 
Fields explained as follows:

Under Procs we have
       r: The number of processes waiting for run time or placed in run queue or are already executing (running)
       b: The number of processes in uninterruptible sleep. (b=blocked queue, waiting for resource (e.g. filesystem I/O blocked, inode lock))

If runnable threads (r) divided by the number of CPU is greater than one -> possible CPU bottleneck

(The (r) coulmn should be compared with number of CPUs (logical CPUs as in uptime) if we have enough CPUs or we have more threads.)

High numbers in the blocked processes column (b) indicates slow disks.

(r) should always be higher than (b); if it is not, it usually means you have a CPU bottleneck

Note: “cat /proc/cpuinfo” dispalys the cpu info on the machine
cat /proc/cpuinfo|grep processor|wc -l
output: 16

Remember that we need to know the number of CPUs on our server because the vmstat r value must never exceed the number of CPUs. r value of 13 is perfectly acceptable for a 16-CPU server, while a value of 16 would be a serious problem for a 12-CPU server.

Whenever the value of the r column exceeds the number of CPUs on the server, tasks are forced to wait for execution. There are several solutions to managing CPU overload, and these alternatives are:
1.      Add more processors (CPUs) to the server.
2.      Load balance the system tasks by rescheduling large batch tasks to execute during off-peak hours.

Under Memory we have:

swpd: shows how many blocks are swapped out to disk (paged). The amount of Virtual memory used.
            Note: you can see the swap area configured in server using "cat proc/swaps"
>cat /proc/swaps
Filename                                Type            Size    Used    Priority
/dev/dm-7                               partition       16777208        21688   -1

free: The amount of Idle Memory
buff: Memory used as buffers, like before/after I/O operations
cache: Memory used as cache by the Operating System

Under Swap we have:

si: Amount of memory swapped in from disk (/s). This shows page-ins
so: Amount of memory swapped to disk (/s). This shows page-outs. The so column is zero consistently, indicating there are no page-outs.

In Ideal condition, si and so should be at 0 most of the time, and we definitely don’t like to see more than 10 blocks per second.

Under IO we have:

bi: Blocks received from block device - Read (like a hard disk)
bo: Blocks sent to a block device – Write

Under System we have:

in: The number of interrupts per second, including the clock.
cs: The number of context switches per second.

(A context switch occurs when the currently running thread is different from the previously running thread, so it is taken off of the CPU.)

It is not uncommon to see the context switch rate be approximately the same as device interrupt rate (in column)

If cs is high, it may indicate too much process switching is occurring, thus using memory inefficiently.

If cs is higher then sy, system is doing more context switching than actual work.

High r with high cs -> possible lock contention
Lock contention occurs whenever one process or thread attempts to acquire a lock held by another process or thread. The more granular the available locks, the less likely one process/thread will request a lock held by the other. (For example, locking a row rather than the entire table, or locking a cell rather than the entire row.)

When you are seeing blocked processes or high values on waiting on I/O (wa), it usually signifies either real I/O issues where you are waiting for file accesses or an I/O condition associated with paging due to a lack of memory on your system.

Under CPU we have:

These are percentages of total CPU time.
       us: % of CPU time spent in user mode (not using kernel code, not able to acces to kernel resources). Time spent running non-kernel code. (user time, including nice time)
       sy: % of CPU time spent running kernel code. (system time)
       id: % of CPU  idle time
       wa: % of CPU time spent waiting for IO.


Note: the memory, swap, and I/O statistics are in blocks, not in bytes. In Linux, blocks are usually 1,024 bytes (1 KB).

To measure true idle time measure id+wa together:
- if id=0%, it does not mean all CPU is consumed, because "wait" (wa) can be 100% and waiting for an I/O to complete

- if wait=0%, it does not mean I have no I/O waiting issues, because as long I have threads which keep the CPU busy I could have additional threads waiting for I/O, but this will be masked by the running threads

If process A is running and process B is waiting on I/O, the wait% still would have a 0 number.

A 0 number doesn't mean I/O is not occurring, it means that the system is not waiting on I/O.

If process A and process B are both waiting on I/O, and there is nothing that can use the CPU, then you would see that column increase.

- if wait% is high, it does not mean I have io performance problem, it can be an indication that I am doing some IO but the cpu is not kept busy at all

- if id% is high then likely there is no CPU or I/O problem


To measure cpu utilization measure us+sy together (and compare it to physc):
- if us+sy is always greater than 80%, then CPU is approaching its limits
 
- if us+sy = 100% -> possible CPU bottleneck

- if sy is high, your appl. is issuing many system calls to the kernel and asking the kernel to work. It measures how heavily the appl. is using kernel services.

- if sy  is higher than us, this means your system is spending less time on real work (not good)

Comments

  1. Great explanations, there are many pages on vmstats but very few go into that much detail. Thanks!

    ReplyDelete
  2. Great work.. Thank you.. This helped me a lot in my work

    ReplyDelete
  3. Thanks a million....Really helped me to understand vmstat!

    ReplyDelete
  4. Thanks! Great explanation

    ReplyDelete
  5. thanks for detailed info

    ReplyDelete
  6. Great explanation. Has been waiting for long to understand vmstat output. Thanks a lot.

    ReplyDelete
  7. Greate explanation.
    But I have a question. How can I know (or get) what is the process (pid) in uninterruptible sleep (under column b)?

    ReplyDelete
  8. can u please tel how to calculate si,so,bi, bo, in, cs, us, sy ,id ,wa, st using /proc/vmstat file ?

    ReplyDelete
  9. Very very nice. Thank you.

    ReplyDelete
  10. Wow !!! excellent xplanation

    ReplyDelete
  11. Simple & Clear. we sincerely appreciate your efforts in writing such a nice article

    ReplyDelete
  12. Simple and clear, well explained.

    ReplyDelete
  13. Perfect explanation :)

    ReplyDelete
  14. Very good explanation.Thanks.

    ReplyDelete
  15. I really appreciate information shared above. It’s of great help. If someone want to learn Online (Virtual) instructor lead live training in R Tool, kindly contact us http://www.maxmunus.com/contact
    MaxMunus Offer World Class Virtual Instructor led training on R Tool. We have industry expert trainer. We provide Training Material and Software Support. MaxMunus has successfully conducted 100000+ trainings in India, USA, UK, Australlia, Switzerland, Qatar, Saudi Arabia, Bangladesh, Bahrain and UAE etc.
    For Demo Contact us:
    Name : Arunkumar U
    Email : arun@maxmunus.com
    Skype id: training_maxmunus
    Contact No.-+91-9738507310
    Company Website –http://www.maxmunus.com


    ReplyDelete
  16. Great work. However, start with vmstat [interval] [count], where interval is the interval between reports and count is the number of times the report is generated.

    ReplyDelete
  17. How do you compare cs to sy to determine if ctxt switching is too high. cs is # of ctxt swtchs and sy is % CPU time in sys mode.

    ReplyDelete

Post a Comment

Popular posts from this blog

Steps to Analyze AWR Report in Oracle

Steps to Analyze AWR Report in Oracle
AWR -Automaticworkload repository is a collection of persistentsystem performancestatisticsowned by SYS. It resides in SYSAUXtablespace. Bydefault snapshot are generated once every 60 min and maintained for 7 days. Each snapshot has a unique ID know as "snap_id". Snapshot detail can be found in "dba_hist_snapshot" view.
If we have Database performance issue and not the Database machine, then AWR Report is the place to look at. AWR is not used for real-time performance monitoring like the v$ tables. It is used for historical analysis of performance. AWR complements, but doesnot replace real-time monitoring.
Once AWR Report is generated in Oracle, the next task is to analyze it. By going through the AWR Report we can easily solve issues like slow database, high wait events, slow query and many more issues. Even though the report is lengthy, Analyzing or Reading relevant part of AWR Report can help to troubleshoot issues in easy and …

Using SQL Developer to create and view Tablespaces

Below are the steps Create and View Table Spaces settings using SQL Developer.
Required SQL developer version is version 3.0
To Create TableSpace :
Click on Menu View/DBA - DBA navigator window will appear.
In the DBA window add a new connection to the DB, and click connect. Then under storage option right click on Tablespaces and choose New Tablespace to create new one. Fill the Details as shown below:


To View the created table spaces: Under Storage, Select Data Files:
It will display the below: