iostat + how to solve latency on disks
we use iostat -x and check for the await column - per device it shows the total time spent waiting plus the actual handling of the request by the disk
iostat -yzx 5
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sdm 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.75 0.00 0.75 0.62 0.10
sda 0.00 0.40 0.00 3.00 0.00 24.70 16.47 0.11 37.60 0.00 37.60 7.13 2.14
sdc 0.00 0.00 0.00 0.80 0.00 6.10 15.25 0.01 12.75 0.00 12.75 12.75 1.02
sdb 0.00 0.00 0.00 0.40 0.00 2.40 12.00 0.01 19.50 0.00 19.50 19.50 0.78
sdd 0.00 0.00 0.00 0.80 0.00 6.60 16.50 0.01 10.75 0.00 10.75 10.75 0.86
sdg 0.00 0.00 0.00 1.00 0.00 8.90 17.80 0.02 15.80 0.00 15.80 15.80 1.58
sdf 0.00 0.20 0.00 1.00 0.00 8.00 16.00 0.01 12.80 0.00 82.80 12.80 1.28
sde 0.00 0.00 0.00 0.80 0.00 7.50 18.75 0.01 11.25 0.00 11.25 11.25 0.90
sdk 0.00 0.00 0.00 0.80 0.00 6.50 16.25 0.01 14.25 0.00 14.25 14.25 1.14
sdi 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 11.60 0.00 11.60 11.60 1.16
sdj 0.00 0.00 0.00 0.80 0.00 5.90 14.75 0.01 13.50 0.00 13.50 13.50 1.08
sdh 0.00 0.00 0.00 0.80 0.00 5.60 14.00 0.01 13.25 0.00 13.25 13.25 1.06
sdl 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 14.20 0.00 14.20 14.20 1.42
sdn 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.88 0.00 0.88 0.75 0.12
md1 0.00 0.00 0.00 0.40 0.00 3.20 16.00
sdq 0.00 0.00 0.00 0.60 0.00 5.20 17.33 0.01 12.67 0.00 82.67 12.67 0.76
sdr 0.00 0.00 0.00 0.60 0.00 4.20 14.00 0.01 10.00 0.00 10.00 10.00 0.60
we can see from the output that await on some disk is high
my question - what we can do about this ?
any option to resolve this ?
linux hard-drive performance redhat-enterprise-linux io
add a comment |
we use iostat -x and check for the await column - per device it shows the total time spent waiting plus the actual handling of the request by the disk
iostat -yzx 5
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sdm 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.75 0.00 0.75 0.62 0.10
sda 0.00 0.40 0.00 3.00 0.00 24.70 16.47 0.11 37.60 0.00 37.60 7.13 2.14
sdc 0.00 0.00 0.00 0.80 0.00 6.10 15.25 0.01 12.75 0.00 12.75 12.75 1.02
sdb 0.00 0.00 0.00 0.40 0.00 2.40 12.00 0.01 19.50 0.00 19.50 19.50 0.78
sdd 0.00 0.00 0.00 0.80 0.00 6.60 16.50 0.01 10.75 0.00 10.75 10.75 0.86
sdg 0.00 0.00 0.00 1.00 0.00 8.90 17.80 0.02 15.80 0.00 15.80 15.80 1.58
sdf 0.00 0.20 0.00 1.00 0.00 8.00 16.00 0.01 12.80 0.00 82.80 12.80 1.28
sde 0.00 0.00 0.00 0.80 0.00 7.50 18.75 0.01 11.25 0.00 11.25 11.25 0.90
sdk 0.00 0.00 0.00 0.80 0.00 6.50 16.25 0.01 14.25 0.00 14.25 14.25 1.14
sdi 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 11.60 0.00 11.60 11.60 1.16
sdj 0.00 0.00 0.00 0.80 0.00 5.90 14.75 0.01 13.50 0.00 13.50 13.50 1.08
sdh 0.00 0.00 0.00 0.80 0.00 5.60 14.00 0.01 13.25 0.00 13.25 13.25 1.06
sdl 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 14.20 0.00 14.20 14.20 1.42
sdn 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.88 0.00 0.88 0.75 0.12
md1 0.00 0.00 0.00 0.40 0.00 3.20 16.00
sdq 0.00 0.00 0.00 0.60 0.00 5.20 17.33 0.01 12.67 0.00 82.67 12.67 0.76
sdr 0.00 0.00 0.00 0.60 0.00 4.20 14.00 0.01 10.00 0.00 10.00 10.00 0.60
we can see from the output that await on some disk is high
my question - what we can do about this ?
any option to resolve this ?
linux hard-drive performance redhat-enterprise-linux io
add a comment |
we use iostat -x and check for the await column - per device it shows the total time spent waiting plus the actual handling of the request by the disk
iostat -yzx 5
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sdm 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.75 0.00 0.75 0.62 0.10
sda 0.00 0.40 0.00 3.00 0.00 24.70 16.47 0.11 37.60 0.00 37.60 7.13 2.14
sdc 0.00 0.00 0.00 0.80 0.00 6.10 15.25 0.01 12.75 0.00 12.75 12.75 1.02
sdb 0.00 0.00 0.00 0.40 0.00 2.40 12.00 0.01 19.50 0.00 19.50 19.50 0.78
sdd 0.00 0.00 0.00 0.80 0.00 6.60 16.50 0.01 10.75 0.00 10.75 10.75 0.86
sdg 0.00 0.00 0.00 1.00 0.00 8.90 17.80 0.02 15.80 0.00 15.80 15.80 1.58
sdf 0.00 0.20 0.00 1.00 0.00 8.00 16.00 0.01 12.80 0.00 82.80 12.80 1.28
sde 0.00 0.00 0.00 0.80 0.00 7.50 18.75 0.01 11.25 0.00 11.25 11.25 0.90
sdk 0.00 0.00 0.00 0.80 0.00 6.50 16.25 0.01 14.25 0.00 14.25 14.25 1.14
sdi 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 11.60 0.00 11.60 11.60 1.16
sdj 0.00 0.00 0.00 0.80 0.00 5.90 14.75 0.01 13.50 0.00 13.50 13.50 1.08
sdh 0.00 0.00 0.00 0.80 0.00 5.60 14.00 0.01 13.25 0.00 13.25 13.25 1.06
sdl 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 14.20 0.00 14.20 14.20 1.42
sdn 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.88 0.00 0.88 0.75 0.12
md1 0.00 0.00 0.00 0.40 0.00 3.20 16.00
sdq 0.00 0.00 0.00 0.60 0.00 5.20 17.33 0.01 12.67 0.00 82.67 12.67 0.76
sdr 0.00 0.00 0.00 0.60 0.00 4.20 14.00 0.01 10.00 0.00 10.00 10.00 0.60
we can see from the output that await on some disk is high
my question - what we can do about this ?
any option to resolve this ?
linux hard-drive performance redhat-enterprise-linux io
we use iostat -x and check for the await column - per device it shows the total time spent waiting plus the actual handling of the request by the disk
iostat -yzx 5
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sdm 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.75 0.00 0.75 0.62 0.10
sda 0.00 0.40 0.00 3.00 0.00 24.70 16.47 0.11 37.60 0.00 37.60 7.13 2.14
sdc 0.00 0.00 0.00 0.80 0.00 6.10 15.25 0.01 12.75 0.00 12.75 12.75 1.02
sdb 0.00 0.00 0.00 0.40 0.00 2.40 12.00 0.01 19.50 0.00 19.50 19.50 0.78
sdd 0.00 0.00 0.00 0.80 0.00 6.60 16.50 0.01 10.75 0.00 10.75 10.75 0.86
sdg 0.00 0.00 0.00 1.00 0.00 8.90 17.80 0.02 15.80 0.00 15.80 15.80 1.58
sdf 0.00 0.20 0.00 1.00 0.00 8.00 16.00 0.01 12.80 0.00 82.80 12.80 1.28
sde 0.00 0.00 0.00 0.80 0.00 7.50 18.75 0.01 11.25 0.00 11.25 11.25 0.90
sdk 0.00 0.00 0.00 0.80 0.00 6.50 16.25 0.01 14.25 0.00 14.25 14.25 1.14
sdi 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 11.60 0.00 11.60 11.60 1.16
sdj 0.00 0.00 0.00 0.80 0.00 5.90 14.75 0.01 13.50 0.00 13.50 13.50 1.08
sdh 0.00 0.00 0.00 0.80 0.00 5.60 14.00 0.01 13.25 0.00 13.25 13.25 1.06
sdl 0.00 0.00 0.00 1.00 0.00 7.20 14.40 0.01 14.20 0.00 14.20 14.20 1.42
sdn 0.00 0.00 0.00 1.60 0.00 4.20 5.25 0.00 0.88 0.00 0.88 0.75 0.12
md1 0.00 0.00 0.00 0.40 0.00 3.20 16.00
sdq 0.00 0.00 0.00 0.60 0.00 5.20 17.33 0.01 12.67 0.00 82.67 12.67 0.76
sdr 0.00 0.00 0.00 0.60 0.00 4.20 14.00 0.01 10.00 0.00 10.00 10.00 0.60
we can see from the output that await on some disk is high
my question - what we can do about this ?
any option to resolve this ?
linux hard-drive performance redhat-enterprise-linux io
linux hard-drive performance redhat-enterprise-linux io
asked Jan 10 at 8:36
King DavidKing David
1931111
1931111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your service times on the relevant disks are around 15ms - this is quite a normal value for spinning rust. Since you have only a very limited amount of outstanding I/O and nearly no reads, you are random write bound. Easiest way to resolve that is using bcache dm-cache or whatever with a decent SSD.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1392651%2fiostat-how-to-solve-latency-on-disks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your service times on the relevant disks are around 15ms - this is quite a normal value for spinning rust. Since you have only a very limited amount of outstanding I/O and nearly no reads, you are random write bound. Easiest way to resolve that is using bcache dm-cache or whatever with a decent SSD.
add a comment |
Your service times on the relevant disks are around 15ms - this is quite a normal value for spinning rust. Since you have only a very limited amount of outstanding I/O and nearly no reads, you are random write bound. Easiest way to resolve that is using bcache dm-cache or whatever with a decent SSD.
add a comment |
Your service times on the relevant disks are around 15ms - this is quite a normal value for spinning rust. Since you have only a very limited amount of outstanding I/O and nearly no reads, you are random write bound. Easiest way to resolve that is using bcache dm-cache or whatever with a decent SSD.
Your service times on the relevant disks are around 15ms - this is quite a normal value for spinning rust. Since you have only a very limited amount of outstanding I/O and nearly no reads, you are random write bound. Easiest way to resolve that is using bcache dm-cache or whatever with a decent SSD.
answered Jan 10 at 8:44
Eugen RieckEugen Rieck
10.1k22128
10.1k22128
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1392651%2fiostat-how-to-solve-latency-on-disks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown