From: Mike Galbraith <bitbucket@online.de>
To: lkml@tigusoft.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very poor latency when using hard drive (raid1)
Date: Tue, 16 Apr 2013 09:24:01 +0200 [thread overview]
Message-ID: <1366097041.4583.13.camel@marge.simpson.net> (raw)
In-Reply-To: <kkis9q$g09$1@ger.gmane.org>
On Tue, 2013-04-16 at 08:49 +0200, lkml@tigusoft.pl wrote:
> On 15/04/13 11:59, lkml@tigusoft.pl wrote:
> > There are 2 hard drives (normal, magnetic) in software raid 1
> > on 3.2.41 kernel.
> >
> > When I write into them e.g. using dd from /dev/zero to a local file
> > (ext4 on default settings), running 2 dd at once (writing two files) it
> > starves all other programs that try to use the disk.
> >
> > Running ls on any directory on same disk (same fs btw), takes over half
> > minute to execute, same for any other disk touching action.
> >
> > Did anyone seen such problem, where too look, what to test?
> >
> > What could solve it (other then ionice on applications that I expect to
> > use hard drive)?
>
> I got reply (by e-mail) suggesting to use XFS.
> Thanks, possible for other/next server.
>
> But I fell this should work correctly as well on ext4.
It should not starve readers that badly, something is wrong.
You can try setting low_latency for the devices if you're using CFQ
ioscheduler. For my box, that would be..
echo 1 > /sys/devices/pci0000:00/0000:00:1f.2/ata2/host0/target0:0:0/0:0:0:0/block/sda/queue/iosched/low_latency
Or, you can try a different scheduler. cat (blabla)/sda/queue/scheduler
to see which choices are available, and echo your choice back to the
file to select it.
-Mike
next prev parent reply other threads:[~2013-04-16 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 9:59 Very poor latency when using hard drive (raid1) lkml
2013-04-16 6:49 ` lkml
2013-04-16 7:24 ` Mike Galbraith [this message]
2013-04-16 11:23 ` Michael Tokarev
2013-04-19 15:01 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1366097041.4583.13.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tigusoft.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.