public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jan Kara <jack@suse.cz>
Subject: Re: Poor desktop responsiveness with background I/O-operations
Date: Mon, 21 Sep 2009 00:04:05 +0200	[thread overview]
Message-ID: <20090920220405.GA395@duck.suse.cz> (raw)
In-Reply-To: <alpine.LRH.2.00.0909202221010.25928@twin.jikos.cz>

On Sun 20-09-09 22:22:20, Jiri Kosina wrote:
> On Sun, 20 Sep 2009, Ulrich Lukas wrote:
> 
> > Test case:
> > - 64-bit dual-core PC, SATA harddrive, plenty of free RAM
> > - vanilla Linux 2.6.31, Kubuntu 9.10 packages, all software 64-bit
> > 
> > 
> > How to reproduce:
> > - start KDE/GNOME-session
> > - open a terminal window and do as a non-root user:
> >   dd if=/dev/zero of=/home/john-doe/testfile
> >   (or dd if=/home/john-doe/big-testfile of=/dev/null)
> > 
> > - a real use scenario would be a daily disk-backup or the
> >   simple extraction of a tarball containing slightly bigger files
> > 
> > 
> > Observation:
> > - The system becomes _really_ slow as described above; unusable for
> >   any multimedia tasks.
> 
> I guess that switching from CFQ to deadline I/O scheduler improves the 
> situation, right?
  For example on my desktop, switching to deadline slightly improves the
situation but the machine is still mostly unusable while dd is running...
I'll try to debug it some more to see whether it can be somehow helped.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2009-09-20 22:04 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
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 [this message]
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=20090920220405.GA395@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=jkosina@suse.cz \
    --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