All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Poor desktop responsiveness with background I/O-operations
Date: Sun, 20 Sep 2009 05:08:43 +0200	[thread overview]
Message-ID: <4AB59CBB.8090907@datenparkplatz.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]

Hi,


using a recent hard-/software setup, I observed that continuous
read/write operations severely degrade the overall system responsiveness
in typical desktop-PC use cases.

Merely doing write/read operations on a data volume leads to stuck text
and mouse cursors, seconds-long delays for simple window-context
switches in X11, dropouts in low-resolution video playback etc.



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.

- Using an encrypted (dm-crypt/LUKS) /home (e.g. on mobile computers)
  compounds the issue to a painful extent.



Possible culprits (I'm guessing) are the Linux I/O- or CPU scheduler.

I realize that a single heavyweight transfer slows down I/O for the
corresponding transactions/processes/volumes etc.

But there needs to be a fair distribution of I/O or CPU time which
leaves enough for other basic operations. And this doesn't seem to be
the case with recent Linux versions.




On a side note, I've tried the BFS-patches (bfs-221 on 2.6.31): This
yields significantly higher throughput when using disk encryption (50%
improvement with dm-crypt/LUKS, 512 bit aes-xts-plain cipher mode). But
with these patches, the responsiveness was even worse during my quick
test. Switching to a text-mode console: several /minutes/ delay...


I'm attaching my .config for linux 2.6.31 (grep ^C and bzip2-ed)


[-- Attachment #2: kernelconfig-linux-2.6.31.bz2 --]
[-- Type: application/octet-stream, Size: 13204 bytes --]

             reply	other threads:[~2009-09-20  3:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20  3:08 Ulrich Lukas [this message]
2009-09-20  4:11 ` Poor desktop responsiveness with background I/O-operations 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
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=4AB59CBB.8090907@datenparkplatz.de \
    --to=stellplatz-nr.13a@datenparkplatz.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.