mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: Poor desktop responsiveness with background I/O-operations
Date: Mon, 21 Sep 2009 15:47:36 -0400	[thread overview]
Message-ID: <m3tyyw6pvz.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <1253520364.25640.57.camel@marge.simson.net> (Mike Galbraith's message of "Mon, 21 Sep 2009 10:06:04 +0200")

FWIW, I did not notice any problems with the last kernel I had compiled
in the -- IIRC -- 29-rc timeframe.  Or maybe it was the 30-rc timeframe.

I had that kernel up for soemthing like five weeks, on a busy, low-ram
laptop, w/o and long pauses or other noticeable pain.  For at least two
years before that the best this laptop could manage before latency
became horrific was a fortnight, and weekly reboots were desirable.

Unfortunately, before I could send out a congratulatory note (I wanted
to first confirm that the result remained) I pulled up and started see-
ing even worse latency then ever.

Turning ext4 barriers off helped avoid some of the new latency, and my
current compile (master as of the 17th) is much better than .31 was.

But long pauses still occur whenever paging and backgound i/o-bound
tasks interact.

There was a major regression in paging performance either .30 or .31
(see above).  Interestingly, top(1) also shows less swap usage for
the same usage patterns than with the older kernels.  I don't know
which is cause or which is effect.

A git pull on a clone of Linus' tree is a great way to trigger the
problem.  As is using Gentoo's portage to install/upgrade anything.
(Bad python; no alligator!¹)  (Yes, that is a burlesque of the no
doughnut joke.)

[1] Pythons which have invaded Florida have reportedly been
    witnessed eating alligators, according to a recent wire
    service article.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

  reply	other threads:[~2009-09-21 19:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20  3:08 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 [this message]
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=m3tyyw6pvz.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=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

all inboxes | Powered by JetHome®