From: Mike Galbraith <efault@gmx.de>
To: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Poor desktop responsiveness with background I/O-operations
Date: Mon, 21 Sep 2009 10:06:04 +0200 [thread overview]
Message-ID: <1253520364.25640.57.camel@marge.simson.net> (raw)
In-Reply-To: <4AB72FDC.5090403@datenparkplatz.de>
On Mon, 2009-09-21 at 09:48 +0200, Ulrich Lukas wrote:
> Hi and thanks for your reply!
Hi.
> Mike Galbraith wrote:
> > nicing a shell or the dd should (and does) help a LOT.
>
> If this is the only way to influence this, maybe the default settings
> for the niceness of interactive and non-interactive tasks are not the
> best choice. (Maybe a distribution problem in this case)
There is no knowledge in the CPU nor IO scheduler wrt interactive vs
non-interactive. I've tinkered many times with a SCHED_INTERACTIVE
class, but it's not at all an easy problem, so keeps landing on the
trash heap. I could ramble on _for ever_ about that subject, but it's
thankfully irrelevant to this thread ;-)
> > reads are sync, more heavily affected by seek latency than writes.
>
> But how does this explain the seconds-long delays?
Seek latencies are cumulative is my (wild arsed) theory.
> If an interactive process causes a lot of seeks because of reads/writes
> which "are sync", I see how this can greatly slow down otherwise
> pipelined write operations, but the other way around?
If you seek between tiny reads, the more little reads you do, the more
seeks hurt. Readahead is supposed to help, but.. the pain is there.
-Mike
next prev parent reply other threads:[~2009-09-21 8:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 3:08 Poor desktop responsiveness with background I/O-operations Ulrich Lukas
2009-09-20 4:11 ` Thomas Fjellstrom
2009-09-20 6:07 ` Arjan van de Ven
2009-09-20 8:50 ` Ulrich Lukas
2009-09-20 17:17 ` Nikos Chantziaras
2009-09-20 19:38 ` Mike Galbraith
2009-09-21 0:22 ` Justin P. Mattock
2009-09-21 4:23 ` Mike Galbraith
2009-09-21 7:48 ` Ulrich Lukas
2009-09-21 8:06 ` Mike Galbraith [this message]
2009-09-21 19:47 ` James Cloos
2009-09-21 22:47 ` Nikos Chantziaras
2009-09-21 23:34 ` James Cloos
2009-09-22 7:06 ` Mike Galbraith
2009-09-22 9:20 ` Mike Galbraith
2009-09-22 11:22 ` Henrique de Moraes Holschuh
2009-09-22 11:32 ` Mike Galbraith
2009-09-22 16:58 ` James Cloos
2009-09-20 17:04 ` Ulrich Lukas
2009-09-20 20:22 ` Jiri Kosina
2009-09-20 22:04 ` Jan Kara
2009-09-21 7:25 ` Mike Galbraith
2009-09-21 7:33 ` Arjan van de Ven
2009-09-21 7:41 ` Mike Galbraith
2009-09-21 7:47 ` Mike Galbraith
2009-09-21 2:59 ` Ulrich Lukas
[not found] <dmlhK-6ws-5@gated-at.bofh.it>
[not found] ` <dmnMy-8tg-7@gated-at.bofh.it>
2009-09-20 18:51 ` Sanjoy Mahajan
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=1253520364.25640.57.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stellplatz-nr.13a@datenparkplatz.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox