Sponsored Content
Operating Systems Solaris Performance (iops) becomes bad, what is the reason? Post 302531457 by ForgetChen on Thursday 16th of June 2011 09:34:25 PM
Old 06-16-2011
the output from "iostat -sndzx 1" is shown as below:

Code:
 
-bash-3.00# iostat -sndzx 1
extended device statistics 
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.2 0.8 3.6 3.6 0.0 0.0 0.0 6.3 0 0 c1t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.5 0 0 c1t2d0
11300.2 0.1 5650.1 0.0 0.2 19.1 0.0 1.7 16 69 c0t661B205100A12200000FB02D0000000Dd0
extended device statistics 
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 167.3 0.0 735.4 0.0 1.0 0.0 6.0 0 98 c1t0d0
16684.4 0.0 8342.2 0.0 0.2 27.8 0.0 1.7 22 100 c0t661B205100A12200000FB02D0000000Dd0
extended device statistics 
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 166.1 0.0 740.8 0.0 1.0 0.0 6.0 0 98 c1t0d0
16858.8 0.0 8429.4 0.0 0.2 27.8 0.0 1.6 22 100 c0t661B205100A12200000FB02D0000000Dd0
extended device statistics 
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 192.0 0.0 847.6 0.0 1.0 0.0 5.1 0 97 c1t0d0
16234.7 0.0 8117.4 0.0 0.2 27.8 0.0 1.7 22 100 c0t661B205100A12200000FB02D0000000Dd0

And you are right, it is doing a bunch of small IO with 512 bytes. The parameter setting of vdbench is shown as following:

Code:
 
sd=sd0,lun=/dev/rdsk/c0t661B205100A12200000FB02D0000000Dd0s2
wd=wd1,sd=(sd*),xfersize=512,rdpct=100,seekpct=0
rd=run1,wd=(wd1),iorate=max,elapsed=900000,interval=1,forthreads=30




Quote:
Originally Posted by achenle
What's the output from

Code:
iostat -sndzx 1

while vdbench is running?

FWIW, it looks like it's doing a bunch of very small IO operations (512 bytes)

Last edited by ForgetChen; 06-16-2011 at 10:53 PM..
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

comparing Huge Files - Performance is very bad

Hi All, Can you please help me in resolving the following problem? My requirement is like this: 1) I have two files YESTERDAY_FILE and TODAY_FILE. Each one is having nearly two million data. 2) I need to check each record of TODAY_FILE in YESTERDAY_FILE. If exists we can skip that by... (5 Replies)
Discussion started by: madhukalyan
5 Replies

2. AIX

Bad performance when log in with putty

Hello guys! I'm n00b in AIX and I'm sticked in a problem. (my English is poor enough, but I hope you can understand me :P). So.. I'm trying to connect to an AIX machine with putty, and .. 'using username xxx' appears after 2 sec (OK), but 'xxx@ip's password' appears after 1:15 min. After... (6 Replies)
Discussion started by: combat2k
6 Replies

3. News, Links, Events and Announcements

Announcing collectl - new performance linux performance monitor

About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies

4. UNIX for Dummies Questions & Answers

nohup has a terrible bad performance compared with interactive command, why?

I have a strange situation. I'm running a shell script containing several data uploads (using Oracle sqlloader utility). This script is being run on a Red Hat server. I tried to run it in background: $ nohup upload.sh & This script uploads some thousands files. After several hours I... (0 Replies)
Discussion started by: viniciov
0 Replies

5. HP-UX

Bad performance but Low CPU loading?

There might be some problem with my server, because every morning at 7, it's performance become bad with no DB extra deadlock. But I just couldn't figure it out. Please give me some advise, thanks a lot... According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%. ... (8 Replies)
Discussion started by: GreenShery
8 Replies

6. Shell Programming and Scripting

Why I get bad bad substitution when using eval?

Why I get bad replace when using eval? $ map0=( "0" "0000" "0") $ i=0 $ eval echo \${map$i} 0000 $ a=`eval echo \${map$i}` !!!error happens!!! bash: ${map$i}: bad substitution How to resolve it ? Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies

7. Solaris

How to measure IOPS?

Hi I have a system running solaris 10, and I intend to use a NetApp as its storage system. The application requires a throughput between the server and the storage 7000 disk IOPS (random IO sustained throughput with response time of 20 mili second and 16k block size). How to make sure that I... (6 Replies)
Discussion started by: fretagi
6 Replies

8. AIX

AIX lpar bad disk I/O performance - 4k per IO limitation ?

Hi Guys, I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0 and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2 There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 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 ] [ -k ] [ -t ] [ -V ] [ -x [ device ] ] [ 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 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 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. %sys Show the percentage of CPU utilization that occurred while executing at the system level (kernel). %idle Show the percentage of time that the CPU or CPUs were idle. 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. The report may show the following fields, depending on whether -x and -k options are used or not: Device: This column gives the device name, which is displayed as hdiskn with 2.2 kernels, for the nth device. It is displayed as devm-n with newer kernels, where m is the major number of the device, and n a distinctive number. When -x option is used, 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. 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 Indicate the amount of data read from the drive expressed in a number of blocks per second. Blocks are equivalent to sectors with post 2.4 kernels 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 drive 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 drive expressed in kilobytes per second. Data displayed are valid only with kernels 2.4 and later. kB_wrtn/s Indicate the amount of data written to the drive expressed in kilobytes per second. Data displayed are valid only with ker- nels 2.4 and later. kB_read The total number of kilobytes read. Data displayed are valid only with kernels 2.4 and later. kB_wrtn The total number of kilobytes written. Data displayed are valid only with kernels 2.4 and later. rrqm/s The number of read requests merged per second that were issued to the device. wrqm/s The number of write requests merged per second that were issued 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. 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. svctm The average service time (in milliseconds) for I/O requests that were issued to the device. %util Percentage of CPU time during which I/O requests were issued to the device. OPTIONS
-c The -c option is exclusive of the -d option and displays only the cpu usage report. -d The -d option is exclusive of the -c option and displays only the device utilization report. -k Display statistics in kilobytes per second instead of blocks per second. Data displayed are valid only with kernels 2.4 and later. -t Print the time for each report displayed. -V Print version number and usage then exit. -x device Display extended statistics. If no device is given on the command line, then extended statistics are displayed for every device reg- istered in the /proc/partitions file. Please note that Linux kernel needs to be patched for this option to work. ENVIRONMENT
The iostat command takes into account the following environment variable: 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 format (YYYY-MM-DD) instead. 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. BUGS
/proc filesystem must be mounted for iostat to work. FILE
/proc/stat contains system statisitics. /proc/partitions contains statistics for the devices. AUTHOR
Sebastien Godard <sebastien.godard@wanadoo.fr> SEE ALSO
vmstat(8), sar(1), mpstat(1) http://perso.wanadoo.fr/sebastien.godard/ Linux JANUARY 2002 IOSTAT(1)
All times are GMT -4. The time now is 09:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy