Solaris10 , disk io sar -d output interpretation
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Question: in sar -d output ..you have %busy column. How is this value calculated? can this value be more than 100%?
solaris disk sar
add a comment |Â
up vote
0
down vote
favorite
Question: in sar -d output ..you have %busy column. How is this value calculated? can this value be more than 100%?
solaris disk sar
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Question: in sar -d output ..you have %busy column. How is this value calculated? can this value be more than 100%?
solaris disk sar
Question: in sar -d output ..you have %busy column. How is this value calculated? can this value be more than 100%?
solaris disk sar
edited Mar 6 at 13:37
Jeff Schaller
31.2k846105
31.2k846105
asked Mar 6 at 13:26
Anil Kumar
1
1
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
How is this value calculated?
This is the percentage of time the device is being read from or written to.
Can it be more than 100%?
No, technically it shouldn't ever be possible for it to be greater than 100%, It can be 100% but this just means that the disk was doing 100% IO operation for the measurement interval.
Being 100% however is not necessarily a bad thing. If you are looking for disk bottle necks you should be more interested in the other stats sar
provides await
,rd_sec/s
,wr_sec/s
...etc
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
How is this value calculated?
This is the percentage of time the device is being read from or written to.
Can it be more than 100%?
No, technically it shouldn't ever be possible for it to be greater than 100%, It can be 100% but this just means that the disk was doing 100% IO operation for the measurement interval.
Being 100% however is not necessarily a bad thing. If you are looking for disk bottle necks you should be more interested in the other stats sar
provides await
,rd_sec/s
,wr_sec/s
...etc
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
add a comment |Â
up vote
0
down vote
How is this value calculated?
This is the percentage of time the device is being read from or written to.
Can it be more than 100%?
No, technically it shouldn't ever be possible for it to be greater than 100%, It can be 100% but this just means that the disk was doing 100% IO operation for the measurement interval.
Being 100% however is not necessarily a bad thing. If you are looking for disk bottle necks you should be more interested in the other stats sar
provides await
,rd_sec/s
,wr_sec/s
...etc
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
add a comment |Â
up vote
0
down vote
up vote
0
down vote
How is this value calculated?
This is the percentage of time the device is being read from or written to.
Can it be more than 100%?
No, technically it shouldn't ever be possible for it to be greater than 100%, It can be 100% but this just means that the disk was doing 100% IO operation for the measurement interval.
Being 100% however is not necessarily a bad thing. If you are looking for disk bottle necks you should be more interested in the other stats sar
provides await
,rd_sec/s
,wr_sec/s
...etc
How is this value calculated?
This is the percentage of time the device is being read from or written to.
Can it be more than 100%?
No, technically it shouldn't ever be possible for it to be greater than 100%, It can be 100% but this just means that the disk was doing 100% IO operation for the measurement interval.
Being 100% however is not necessarily a bad thing. If you are looking for disk bottle necks you should be more interested in the other stats sar
provides await
,rd_sec/s
,wr_sec/s
...etc
answered Mar 6 at 14:47
alpha
1,241317
1,241317
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
add a comment |Â
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
device %busy avque r+w/s blks/s avwait avserv sd5 171 474.2 472 13333 158.7 846 sd5,a 0 0 0 0 0 0 sd5,b 0 0 0 0 0 0 sd5,c 0 0 0 0 0 0 sd5,d 0 0 0 0 0 0 sd5,e 166 28 0 0 0 0 sd5,f 241 21.2 5 4867 1442.1 3026.3 sd5,g 0 0 0 0 0 0 sd5,h 171 440.3 469 9878 136.8 802.8 when i look at the sar data it looks like this..it has values 171..
â Anil Kumar
Mar 8 at 15:21
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428507%2fsolaris10-disk-io-sar-d-output-interpretation%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password