Sponsored Content
Full Discussion: Iostat inconsistent avgrq-sz
Top Forums UNIX for Advanced & Expert Users Iostat inconsistent avgrq-sz Post 302922726 by maverick_here on Tuesday 28th of October 2014 02:53:02 AM
Old 10-28-2014
RedHat Iostat inconsistent avgrq-sz

Hi Experts,

I have an issue with performance of oracle, the db sits on EBS volumes on and aws EC2 instance. I have captured the iostat data and feed it to iostat_plotter to forward it to the DB administrators. However what I'm trying to understand is the variable avgrq-sz, it is quite in consistent.

The system is running RHEL 6.4 64 bit, Oracle 11g. The block size is 4K .Following is the extract for two devices which are of interest

Code:
Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
xvdj              0.00    80.55   15.18   59.58  1155.01  1121.04    30.45     1.10   14.74   0.70   5.20
xvdj              0.00     0.00    3.00    2.00    48.00    16.00    12.80     0.03    5.80   5.60   2.80
xvdj              0.00     0.00   14.00  162.00   704.00  1296.00    11.36     0.34    1.94   0.87  15.30
xvdj              0.00     0.00    8.00    4.00   304.00    32.00    28.00     0.15   12.25   5.50   6.60
xvdj              0.00     0.00    0.00    1.00     0.00     8.00     8.00     0.00    1.00   1.00   0.10
xvdj              0.00   114.00    2.00  147.00    96.00  2088.00    14.66     0.86    5.77   0.58   8.60
xvdj              0.00     0.00    0.00   33.00     0.00   264.00     8.00     0.05    1.42   0.48   1.60
xvdj              0.00     0.00    4.00    6.00    64.00    48.00    11.20     0.08    7.60   7.00   7.00
xvdj              0.00     0.00    6.00   60.00    96.00   480.00     8.73     0.17    2.56   1.80  11.90
xvdj              0.00     0.00    4.00    3.00    64.00    24.00    12.57     0.10   15.00  14.71  10.30

and

Code:
Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
xvdk              0.00     0.09   38.83   28.48  2696.19   228.51    43.45     0.35    5.24   1.29   8.67
xvdk              0.00     0.00  187.00    3.00  5440.00    24.00    28.76     2.65   14.23   5.26 100.00
xvdk              0.00     0.00  330.00   14.00 12592.00   112.00    36.93     3.54   10.15   2.91 100.00
xvdk              0.00     0.00  270.00    0.00  9968.00     0.00    36.92     4.01   14.99   3.70 100.00
xvdk              0.00     0.00  269.00    0.00  8336.00     0.00    30.99     3.27   12.20   3.72 100.00
xvdk              0.00     0.00  249.00    0.00  8496.00     0.00    34.12     3.50   13.47   4.02 100.00
xvdk              0.00     0.00  261.00    0.00  8432.00     0.00    32.31     3.35   13.19   3.83 100.00
xvdk              0.00     0.00  255.00    3.00  8944.00    24.00    34.76     3.56   13.94   3.88 100.00
xvdk              0.00     0.00  255.00   12.00  7872.00    96.00    29.84     3.04   11.38   3.75 100.10
xvdk              0.00     0.00  281.00    0.00  9424.00     0.00    33.54     3.03   10.79   3.56  99.90

These samples are one sec apart. My first guess is that the data sets which are being processed by oracle need reindexing.

Any suggestions would be highly appreciated
 

10 More Discussions You Might Find Interesting

1. HP-UX

Why are these inconsistent?

Hi I am using HP - UX... When I execute the below commands I get these results... Why do i get a different shell value when i run echo $SHELL? # echo $0 ksh # echo $SHELL sh # ps -p$$ PID TTY TIME COMMAND 4013 pts/7 0:00 ksh (2 Replies)
Discussion started by: gurubarancse
2 Replies

2. Shell Programming and Scripting

Inconsistent variable assignment issue

I am using a piece of code which is working fine in some cases and is not working in some other instances. All I am doing is grep'ing and concatenating. Below is a working scenario. $ echo $var1 REPLYFILENAME=Options_NSE1.txt.enc $ FILE_NM=`echo ${var1##*=}`.gz (Take everything after... (1 Reply)
Discussion started by: jamjam10k
1 Replies

3. Shell Programming and Scripting

AWK with inconsistent field layout

Input File: 1234567890123456789012345678901234 ---------------------------------- 11111 XXX xxxxx 6666666666 22222 YYY 2222222222 33333 AAA TTT xxxxx 9999999999 44444 55555 RRR UUU 5555555555 66666 TTT nnnnn 2222222222 77777 XXX ... (4 Replies)
Discussion started by: lordsmiter
4 Replies

4. UNIX for Advanced & Expert Users

inconsistent cat output

Hi I'm executing a menu script in which I `cat a file` but it's giving different output some times. Following is the code fragment taken from my script. while true do cat procs.configured echo ---------separator-------------- sleep 3 done when I execute this code fragment, `cat` outputs... (2 Replies)
Discussion started by: axes
2 Replies

5. Shell Programming and Scripting

ps -eaf gives inconsistent result

The command ps -eaf gives inconsistent result when executed on XYZ server (the command shows 1, 2 or 3 instances of the process. Ideally it should show only 1). I have attached the script file that was executed and the corresponding output. When the same script was executed on ABC server it gave... (1 Reply)
Discussion started by: rebels
1 Replies

6. Shell Programming and Scripting

inconsistent output using date()

I have an input list of: I am just trying to turn this list into its seconds since epoch "+%s" time equivalent. I'm trying to use the following, but every time I run the command it gives me different answers, they are close, but never the same... any clues as to why? xargs -I{} date -j -f... (3 Replies)
Discussion started by: mdlloyd7
3 Replies

7. Shell Programming and Scripting

Inconsistent column printing

Hi, I have a file that has inconsistently numbered columns. Like row1 has 23 columns, and row 2 has 34 columns etc. I would like to re-order the first 8 columns as required and from the 9th column till the end, I would like to print it as it is. I tried to read the re-ordered 8 columns... (7 Replies)
Discussion started by: jacobs.smith
7 Replies

8. Shell Programming and Scripting

Inconsistent behavior when sorting by column

I'm trying to sort the list below, so that multiple instances of the form pass=i_d=j are contiguous. Curiously, the standard sort command to do this works some of the time (it produced the output below) but not all of the time. the command I used was cat fileName | sort -k1.26,1.26n... (3 Replies)
Discussion started by: LeoKSimon
3 Replies

9. UNIX for Advanced & Expert Users

Inconsistent disk information.

On one of the Unix server B.11.31. a disk that has been provisioned from the VMAX, but according to the diskinfo its show coming from clarion. sudo /opt/emc/SYMCLI/bin/symvg sho /dev/vg_<name> Volume Group Name : /dev/vg_<name> Volume Group Type : HP-UX LVM Volume Group State ... (0 Replies)
Discussion started by: kpatel786
0 Replies

10. UNIX for Beginners Questions & Answers

Inconsistent results using sort function

Could you please advise on the following: I have two space-delimited files with 9 and 10 columns, respectively, with exactly the same values in column 1. However, the order of column 1 differs between the two files, so I want to sort both files by column 1, so that I can align them and... (6 Replies)
Discussion started by: aberg
6 Replies
IOSTAT(1)                                                       Linux User's Manual                                                      IOSTAT(1)

NAME
iostat - Report Central Processing Unit (CPU) statistics and input/output statistics for devices and partitions. SYNOPSIS
iostat [ -c ] [ -d ] [ -h ] [ -N ] [ -k | -m ] [ -t ] [ -V ] [ -x ] [ -z ] [ [ [ -T ] -g group_name ] { 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 systems, 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. 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 collected during the interval since the previous report. The count param- eter 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 parameter is specified without the count parameter, the iostat com- mand generates reports continuously. REPORTS
The iostat command generates three types of reports, the CPU Utilization report, the Device Utilization report and the Network Filesystem 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 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 servicing 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 and partitions for which statistics are to be displayed may be entered on the com- mand line. 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. Transfer rates are shown in 1K blocks by default, unless the environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used. The report may show the following fields, depending on the flags used: Device: This column gives the device (or partition) name as listed in the /dev directory. tps Indicate the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Mul- tiple logical requests can be combined into a single I/O request to the device. A transfer is of indeterminate size. Blk_read/s (kB_read/s, MB_read/s) Indicate 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. Blk_wrtn (kB_wrtn, MB_wrtn) The total number of blocks (kilobytes, 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 (after merges) of read requests completed per second for the device. w/s The number (after merges) of write requests completed per second for the device. rsec/s (rkB/s, rMB/s) The number of sectors (kilobytes, megabytes) read from the device per second. wsec/s (wkB/s, wMB/s) The number of sectors (kilobytes, 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 servicing them. r_await The average time (in milliseconds) for read requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. w_await The average time (in milliseconds) for write requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing 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%. OPTIONS
-c Display the CPU utilization report. -d Display the device utilization report. -g group_name { device [...] | ALL } Display statistics for a group of devices. The iostat command reports statistics for each individual device in the list then a line of global statistics for the group displayed as group_name and made up of all the devices in the list. The ALL keyword means that all the block devices defined by the system shall be included in the group. -h Make the Device Utilization Report easier to read by a human. -k Display statistics in kilobytes per second. -m Display statistics in megabytes per second. -N Display the registered device mapper names for any device mapper devices. Useful for viewing LVM2 statistics. -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 sta- tistics have to be displayed for all the block devices and partitions defined by the system, including those that have never been used. -T This option must be used with option -g and indicates that only global statistics for the group are to be displayed, and not statis- tics for individual devices in the group. -t Print the time for each report displayed. The timestamp format may depend on the value of the S_TIME_FORMAT environment variable (see below). -V Print version number then exit. -x Display extended statistics. -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 variables: 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. POSIXLY_CORRECT When this variable is set, transfer rates are shown in 512-byte blocks instead of the default 1K blocks. 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 sda sdb 2 6 Display six reports of extended statistics at two second intervals for devices sda and sdb. 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. Kernels older than 2.6.x are no longer supported. 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/diskstats contains disks statistics. /sys contains statistics for block devices. /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), nfsiostat(1), cifsiostat(1) http://pagesperso-orange.fr/sebastien.godard/ Linux MAY 2012 IOSTAT(1)
All times are GMT -4. The time now is 03:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy