Skip to main content

iostat command and options

iostat - Report Central Processing Unit (CPU) statistics and input/output statistics for devices and partitions. It is used for monitoring system input/output device loading by observing the time the devices are active in relation to their average transfer rates.The iostat command generates reports that can be used to change system configuration to better balance the input/output load between physical disks.
The first report generated by the iostat command provides statistics concerning the time since the system was booted, unless the -y  option is used (in this case, this first report is omitted).  Each subsequent report covers the time since the previous report.
Type the following command:
$iostat
Screenshot from 2015-07-22 11:13:36.png
REPORTS
The iostat command generates two types of reports, the CPU Utilization report and the Device Utilization report.
CPU Utilization Report - The first report generated by the iostat command is the CPU Utilization Report. For multiprocessor systems, the CPU values are global averages among all processors. The report has the following format:
%user shows the percentage of CPU utilization that occurred while executing at the user level (application).
%nice shows the percentage of CPU utilization that occurred while executing at the user level with nice priority.
%system shows the percentage of CPU utilization that occurred while executing at the system level (kernel).
%iowait shows the percentage of time that the CPU or CPUs were idle during which the system had an outstanding disk I/O request.
%steal    shows the  percentage of time spent in involuntary wait by the virtual CPU or CPUs while the hypervisor was servicing another virtual processor.
%idle shows the percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request.
Device Utilization Report - The second report generated by the iostat command is the Device Utilization Report. The device report provides statistics on a per physical device or partition basis. Block devices and partitions for which statistics are to be displayed may be entered on the command line. If no device nor partition is entered, then statistics are displayed for every device used by the system. The report may show the following fields, depending on the flags used:

More on device file here - http://www.cyberciti.biz/faq/understanding-unix-linux-bsd-device-files/ 
Device: This column gives the device (or partition) name as listed in the /dev directory. As you can see from snapshot above that I have only one device.
tps indicates the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Multiple logical requests can be combined into a single I/O request to the device.
Blk_read/s (kB_read/s, MB_read/s) indicates the amount of data read from the device expressed in a number of blocks (kilobytes, megabytes) per second. Blocks are equivalent to sectors and therefore have a size of 512 bytes.
Blk_wrtn/s (kB_wrtn/s, MB_wrtn/s) Indicate the amount of data written to the device expressed in a number of blocks (kilobytes, megabytes) per second.
Blk_read (kB_read, MB_read) The total number of blocks (kilobytes, megabytes) read.
OPTIONS
  -c     Display the CPU utilization report.
$ iostat -c
Screenshot from 2015-07-22 11:44:52.png
  -d     Display the device utilization report.
    $ iostat -d
Screenshot from 2015-07-22 11:46:27.png

Popular posts from this blog

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos .     Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Real Time JMeter Result Using Backend Listener

Since JMeter 2.13 Backend Listener has been available to create real time graph of JMeter Test. Following tutorial explain the entire process in detail. At the end of this tutorial you would be able to create JMeter Live Test Result dashboard similar to following - This tutorial borrows information from many sources and my own experiments with JMeter live reporting dashboard. I have added source of information wherever applicable But before we can build such a snazzy JMeter Live Reporting dashboard we need to understand two more components - influxDB (a time series database) and Grafana Dashboard This is a big tutorial, so take deep breath :-) and follow on. Once you complete set up specified in this tutorial then you can watch JMeter Training Video Tutorial to watch this in action. What is Time Series Database? A time series is a sequence of data points , typically consisting of successive measurements made over a time interval . Examples of time ...