Linux User's Manual IOSTAT
IOSTAT(1) Linux User's Manual IOSTAT(1)
NAME
iostat - Report Central Processing Unit (CPU) statistics and input/out-
put statistics for devices, partitions and network filesystems (NFS).
SYNOPSIS
iostat [ -c ] [ -d ] [ -N ] [ -n ] [ -h ] [ -k | -m ] [ -t ] [ -V ] [
-x ] [ -z ] [ device [...] | ALL ] [ -p [ device [,...] | ALL ] ] [
interval [ count ] ]
DESCRIPTION
The iostat command 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. Each subsequent report
covers the time since the previous report. All statistics are reported
each time the iostat command is run. The report consists of a CPU
header row followed by a row of CPU statistics. On multiprocessor sys-
tems, CPU statistics are calculated system-wide as averages among all
processors. A device header row is displayed followed by a line of
statistics for each device that is configured. When option -n is used,
an NFS header row is displayed followed by a line of statistics for
each network filesystem that is mounted.
The interval parameter specifies the amount of time in seconds between
each report. The first report contains statistics for the time since
system startup (boot). Each subsequent report contains statistics col-
lected during the interval since the previous report. The count parame-
ter can be specified in conjunction with the interval parameter. If the
count parameter is specified, the value of count determines the number
of reports generated at interval seconds apart. If the interval parame-
ter is specified without the count parameter, the iostat command gener-
ates reports continuously.
REPORTS
The iostat command generates three types of reports, the CPU Utiliza-
tion report, the Device Utilization report and the Network Filesystem
report.
CPU Utilization Report
The first report generated by the iostat command is the CPU Uti-
lization Report. For multiprocessor systems, the CPU values are
global averages among all processors. The report has the fol-
lowing format:
%user
Show the percentage of CPU utilization that occurred
while executing at the user level (application).
%nice
Show the percentage of CPU utilization that occurred
while executing at the user level with nice priority.
%system
Show the percentage of CPU utilization that occurred
while executing at the system level (kernel).
%iowait
Show the percentage of time that the CPU or CPUs were
idle during which the system had an outstanding disk I/O
request.
%steal
Show the percentage of time spent in involuntary wait by
the virtual CPU or CPUs while the hypervisor was servic-
ing another virtual processor.
%idle
Show 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 for which
statistics are to be displayed may be entered on the command
line. Partitions may also be entered on the command line provid-
ing that option -x is not used. If no device nor partition is
entered, then statistics are displayed for every device used by
the system, and providing that the kernel maintains statistics
for it. If the ALL keyword is given on the command line, then
statistics are displayed for every device defined by the system,
including those that have never been used. The report may show
the following fields, depending on the flags used:
Device:
This column gives the device (or partition) name, which
is displayed as hdiskn with 2.2 kernels, for the nth
device. It is displayed as devm-n with 2.4 kernels, where
m is the major number of the device, and n a distinctive
number. With newer kernels, the device name as listed in
the /dev directory is displayed.
tps
Indicate 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. A transfer is of inde-
terminate size.
Blk_read/s
Indicate the amount of data read from the device
expressed in a number of blocks per second. Blocks are
equivalent to sectors with kernels 2.4 and later and
therefore have a size of 512 bytes. With older kernels, a
block is of indeterminate size.
Blk_wrtn/s
Indicate the amount of data written to the device
expressed in a number of blocks per second.
Blk_read
The total number of blocks read.
Blk_wrtn
The total number of blocks written.
kB_read/s
Indicate the amount of data read from the device
expressed in kilobytes per second.
kB_wrtn/s
Indicate the amount of data written to the device
expressed in kilobytes per second.
kB_read
The total number of kilobytes read.
kB_wrtn
The total number of kilobytes written.
MB_read/s
Indicate the amount of data read from the device
expressed in megabytes per second.
MB_wrtn/s
Indicate the amount of data written to the device
expressed in megabytes per second.
MB_read
The total number of megabytes read.
MB_wrtn
The total number of megabytes written.
rrqm/s
The number of read requests merged per second that were
queued to the device.
wrqm/s
The number of write requests merged per second that were
queued to the device.
r/s
The number of read requests that were issued to the
device per second.
w/s
The number of write requests that were issued to the
device per second.
rsec/s
The number of sectors read from the device per second.
wsec/s
The number of sectors written to the device per second.
rkB/s
The number of kilobytes read from the device per second.
wkB/s
The number of kilobytes written to the device per second.
rMB/s
The number of megabytes read from the device per second.
wMB/s
The number of megabytes written to the device per second.
avgrq-sz
The average size (in sectors) of the requests that were
issued to the device.
avgqu-sz
The average queue length of the requests that were issued
to the device.
await
The average time (in milliseconds) for I/O requests
issued to the device to be served. This includes the time
spent by the requests in queue and the time spent servic-
ing them.
svctm
The average service time (in milliseconds) for I/O
requests that were issued to the device. Warning! Do not
trust this field any more. This field will be removed in
a future sysstat version.
%util
Percentage of CPU time during which I/O requests were
issued to the device (bandwidth utilization for the
device). Device saturation occurs when this value is
close to 100%.
Network Filesystem report
The Network Filesystem (NFS) report provides statistics for each
mounted network filesystem. The report shows the following
fields:
Filesystem:
This columns shows the hostname of the NFS server fol-
lowed by a colon and by the directory name where the net-
work filesystem is mounted.
rBlk_nor/s
Indicate the number of blocks read by applications via
the read(2) system call interface. A block has a size of
512 bytes.
wBlk_nor/s
Indicate the number of blocks written by applications via
the write(2) system call interface.
rBlk_dir/s
Indicate the number of blocks read from files opened with
the O_DIRECT flag.
wBlk_dir/s
Indicate the number of blocks written to files opened
with the O_DIRECT flag.
rBlk_svr/s
Indicate the number of blocks read from the server by the
NFS client via an NFS READ request.
wBlk_svr/s
Indicate the number of blocks written to the server by
the NFS client via an NFS WRITE request.
rkB_nor/s
Indicate the number of kilobytes read by applications via
the read(2) system call interface.
wkB_nor/s
Indicate the number of kilobytes written by applications
via the write(2) system call interface.
rkB_dir/s
Indicate the number of kilobytes read from files opened
with the O_DIRECT flag.
wkB_dir/s
Indicate the number of kilobytes written to files opened
with the O_DIRECT flag.
rkB_svr/s
Indicate the number of kilobytes read from the server by
the NFS client via an NFS READ request.
wkB_svr/s
Indicate the number of kilobytes written to the server by
the NFS client via an NFS WRITE request.
rMB_nor/s
Indicate the number of megabytes read by applications via
the read(2) system call interface.
wMB_nor/s
Indicate the number of megabytes written by applications
via the write(2) system call interface.
rMB_dir/s
Indicate the number of megabytes read from files opened
with the O_DIRECT flag.
wMB_dir/s
Indicate the number of megabytes written to files opened
with the O_DIRECT flag.
rMB_svr/s
Indicate the number of megabytes read from the server by
the NFS client via an NFS READ request.
wMB_svr/s
Indicate the number of megabytes written to the server by
the NFS client via an NFS WRITE request.
ops/s
Indicate the number of operations that were issued to the
filesystem per second.
rops/s
Indicate the number of 'read' operations that were issued
to the filesystem per second.
wops/s
Indicate the number of 'write' operations that were
issued to the filesystem per second.
OPTIONS
-c Display the CPU utilization report.
-d Display the device utilization report.
-h Make the NFS report displayed by option -n easier to read by a
human.
-k Display statistics in kilobytes per second instead of blocks per
second. Data displayed are valid only with kernels 2.4 and
later.
-m Display statistics in megabytes per second instead of blocks or
kilobytes per second. Data displayed are valid only with ker-
nels 2.4 and later.
-N Display the registered device mapper names for any device mapper
devices. Useful for viewing LVM2 statistics.
-n Display the network filesystem (NFS) report. This option works
only with kernel 2.6.17 and later.
-p [ { device [,...] | ALL } ]
The -p option displays statistics for block devices and all
their partitions that are used by the system. If a device name
is entered on the command line, then statistics for it and all
its partitions are displayed. Last, the ALL keyword indicates
that statistics have to be displayed for all the block devices
and partitions defined by the system, including those that have
never been used. Note that this option works only with post 2.5
kernels.
-t Print the time for each report displayed. The timestamp format
may depend on the value of the S_TIME_FORMAT environment vari-
able (see below).
-V Print version number then exit.
-x Display extended statistics. This option works with post 2.5
kernels since it needs /proc/diskstats file or a mounted sysfs
to get the statistics. This option may also work with older ker-
nels (e.g. 2.4) only if extended statistics are available in
/proc/partitions (the kernel needs to be patched for that).
-z Tell iostat to omit output for any devices for which there was
no activity during the sample period.
ENVIRONMENT
The iostat command takes into account the following environment vari-
able:
S_TIME_FORMAT
If this variable exists and its value is ISO then the current
locale will be ignored when printing the date in the report
header. The iostat command will use the ISO 8601 format (YYYY-
MM-DD) instead. The timestamp displayed with option -t will
also be compliant with ISO 8601 format.
EXAMPLES
iostat
Display a single history since boot report for all CPU and
Devices.
iostat -d 2
Display a continuous device report at two second intervals.
iostat -d 2 6
Display six reports at two second intervals for all devices.
iostat -x hda hdb 2 6
Display six reports of extended statistics at two second inter-
vals for devices hda and hdb.
iostat -p sda 2 6
Display six reports at two second intervals for device sda and
all its partitions (sda1, etc.)
BUGS
/proc filesystem must be mounted for iostat to work.
Extended statistics are available only with post 2.5 kernels.
The average service time (svctm field) value is meaningless, as I/O
statistics are calculated at block level, and we don't know when the
disk driver starts to process a request. For this reason, this field
will be removed in a future sysstat version.
FILES
/proc/stat contains system statistics.
/proc/uptime contains system uptime.
/proc/partitions contains disk statistics (for pre 2.5 kernels that
have been patched).
/proc/diskstats contains disks statistics (for post 2.5 kernels).
/sys contains statistics for block devices (post 2.5 kernels).
/proc/self/mountstats contains statistics for network filesystems.
AUTHOR
Sebastien Godard (sysstat <at> orange.fr)
SEE ALSO
sar(1), pidstat(1), mpstat(1), vmstat(8)
http://pagesperso-orange.fr/sebastien.godard/
Linux APRIL 2009 IOSTAT(1)
Linux User's Manual IOSTAT的更多相关文章
- linux常用命令:iostat 命令
Linux系统中的 iostat 是I/O statistics(输入/输出统计)的缩写,iostat工具将对系统的磁盘操作活动进行监视.它的特点是汇报磁盘活动统计情况,同时也会 汇报出CPU使用情况 ...
- Linux命令详解----iostat
Linux系统出现了性能问题,一般我们可以通过top.iostat.free.vmstat等命令来查看初步定位问题.在一个以前看到系统监控工具,总在想那些监控工具的代理,如何收集系统性能信息,io性能 ...
- Linux Programmer's Manual --- reboot
REBOOT(2) Linux Programmer's Manual REBOOT(2) NAME reboot - reboot or enable/disable Ctrl-Alt-Del SY ...
- Linux监控工具介绍系列——iostat
文章转自:https://www.cnblogs.com/ghj1976/p/5691857.html Linux系统中的 iostat是I/O statistics(输入/输出统计)的缩写,iost ...
- [Linux 性能检测工具]IOSTAT
IOSTAT NAME: Iostat, 报告CPU的统计,和 I/O的统计. 语法: iostat [ -c ] [ -d ] [ -N ] [ -n ] [ -h ] [ -k ...
- linux性能调试之iostat
iostat用来监控调试linux系统的IO性能. 一般用法: iostat -xdct time_interval count [disk] -x:显示扩展统计项,如果不使用-x参数只会打印基本统计 ...
- Linux性能分析top iostat vmstat free
最近看到一大牛的分析报告,才知道笔者认识这4个命令是多么肤浅,其实要读懂内存的信息,是要一些功力的.1.top VIRT 虚拟内存总量,VIRT=SWAP+RESSWAP ...
- 【转】Linux IO实时监控iostat命令详解
转自:http://www.cnblogs.com/ggjucheng/archive/2013/01/13/2858810.html 简介 iostat主要用于监控系统设备的IO负载情况,iosta ...
- Linux IO实时监控iostat命令详解
简介 iostat主要用于监控系统设备的IO负载情况,iostat首次运行时显示自系统启动开始的各项统计信息,之后运行iostat将显示自上次运行该命令以后的统计信息.用户可以通过指定统计的次数和时间 ...
随机推荐
- C# 构造函数的使用方法
C#构造函数是一个特殊的类方法.在很多方面,包括访问修饰符.重载以及参数列表的语法等方面,构造函数与普通的方法是类似的.然而,在使用方面以及行为方面,构造函数也具有许多特殊的语法和语义规则. 下面列出 ...
- POJ2485Highways
http://poj.org/problem?id=2485 题意 : 这道题和1258很像,但是这道题求的是最小生成树中最大的那条边,所以在函数里处理一下就行了. 思路 : 赤裸裸的最小生成树啊,但 ...
- Linux查看随机启动服务
Liunx操作系统跟Windos XP一样,有一批系统服务随机而启动:略懂电脑的Windows XP用户会禁止那些不必要的服务,以提高开机速度:如今安装了Ubuntu操作系统,咱们也有必要了解Ubun ...
- 欧拉工程第72题:Counting fractions
题目链接:https://projecteuler.net/problem=72 真分数;n/d 当d ≤ 1,000,000时候的真分数有多少个 public class P72{ void run ...
- 再谈PCA
其实之前写过PCA相关的博文,但是由于之前掌握的理论知识有限,所以理解也比较浅.这篇博文,我们以另外一种角度来理解PCA看,这里我假设大家对PCA都有一个初步的了解.首先,我们举一个二维空间中 ...
- PHP中的多态
多态的概念一般是强类型语言来谈的,因为强类型语言它必须要声明参数类型,比如一个手电筒对象的打开方法其参数申明了只能是蓝光,就不能传其他光.但可以用父类渲染的方式使其多态,比如声明一个光的父类,让其它颜 ...
- 用于主题检测的临时日志(383b4f88-5dc7-4b08-a585-27104eb4ee7f - 3bfe001a-32de-4114-a6b4-4005b770f6d7)
这是一个未删除的临时日志.请手动删除它.(1e2a0af2-731b-4f82-9aa0-4e2d10ed7a1a - 3bfe001a-32de-4114-a6b4-4005b770f6d7)
- Windows系统上如何使用SSH
Windows系统上如何使用SSH 传统的网络服务程序如FTP.Telnet等,在网络上一般使用明文传送数据.用户账号和口令信息,容易受到中间人的攻击.用户利用SSH协议后能有效防止DNS及IP欺骗, ...
- JavaMail如何保证邮件发送成功
使用过JavaMail的api发送邮件的人可能会有这样一个疑惑:我如何知道我调用该api发送的邮件是否成功呢?一般的开放的api给我们调用都会有个返回值或者状态码,来告诉我们执行成功与否.但是Java ...
- android从应用到驱动之—camera(1)---程序调用流程
一.开篇 写博客还得写开篇介绍,可惜,这个不是我所擅长的.就按我自己的想法写吧. 话说camera模块,从上层到底层一共包含着这么几个部分: 1.apk------java语言 2.camera的ja ...