Skip to main content

iostat command and options- Performance Measurement commands for Unix

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






















Labels:

Comments

Post a Comment

Popular posts from this blog

A Tutorial to Send Email using JMeter

Sending email is a mundane activity in any professional’s life. It’s a common medium for communication nowadays. Therefore performance testing of email server is not only important but necessary for an organization. JMeter can be helpful to perform load testing in such scenarios. In this tutorial, we will see how JMeter can be used to send email. We will use SMTP Sampler of JMeter to send an email. JavaMail API is needed to enable email functionality in JMeter. Download it from  here  and paste the jar in JMeter’s lib folder. Now, perform below steps to configure SMTP Sampler. Add a new Thread Group under Test Plan. Right click on Thread Group and select Add–>Sampler–>SMTP Sampler. We need to populate SMTP server’s details in this sampler. We will use GMail for sending an email. For this, enter these values in SMTP Sampler fields. Server: smtp.googlemail.com, Port: 587. Provide values in Email Address From and To fields of Mail Settings section to specify sender...
Post a Comment
Read more

JMeter Exceeded Maximum Number of Redirects Error Solution

While running performance test, JMeter allows maximum 5 redirects by default. However, if your system demands more than 5 redirects, it may result in JMeter exceeded maximum number of redirects error. In this post, we have listed down steps to overcome this error. Actual error in JMeter: Response code: “Non HTTP response code: java.io.IOException” Response message: “Non HTTP response message: Exceeded maximum number of redirects: 5” This error is noticed because  JMeter  allows maximum 5 redirects by default and your system may be using more than 5 redirects. You need to increase this count to more than 5 in jmeter.properties file. Follow below steps to achieve this. Navigate to /bin directory of your JMeter installation. Locate jmeter.properties file and open it in any editor. Search for “httpsampler.max_redirects” property in opened file. Uncomment the above property by removing # before it. Change to value to more than 5 Eg. 20. Save the file and restart JMet...
Post a Comment
Read more

Difference Between Redirect Automatically and Follow Redirects in JMeter

In this post, we will highlight important difference between Redirect Automatically and Follow Redirects options. These options are found in HTTP Request sampler of JMeter. Knowing the difference will help you decide your performance test strategy. When you check Redirect Automatically option, JMeter will not consider redirect as separate HTTP request. This in turn may result as lower response time in your overall performance test. Whereas Follow Redirect option will consider each redirection as separate requests. This may result in comparatively higher response time. This only has any effect if “Redirect Automatically” is not enabled. To see the difference between these two, record a sample script and run it by checking Redirect Automatically and Follow Redirects option. The second option will generate more requests in your result listener. As you can see from the above post, knowing the difference between Redirect Automatically and Follow Redirects option makes difference i...
Post a Comment
Read more