All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Andrew Morton <akpm@osdl.org>,
	Martin Konold <martin.konold@erfrakon.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Interactive Usage of 2.6.0.test1 worse than 2.4.21
Date: Wed, 06 Aug 2003 10:55:33 +1000	[thread overview]
Message-ID: <3F305205.2010705@cyberone.com.au> (raw)
In-Reply-To: <16176.13066.601441.179810@wombat.chubb.wattle.id.au>



Peter Chubb wrote:

>>>>>>"Andrew" == Andrew Morton <akpm@osdl.org> writes:
>>>>>>
>
>Andrew> Martin Konold <martin.konold@erfrakon.de> wrote:
>
>>>Hi,
>>>
>>>when using 2.6.0.test1 on a high end laptop (P-IV 2.2 GHz, 1GB RAM)
>>>I notice very significant slowdown in interactive usage compared to
>>>2.4.21.
>>>
>>>The difference is most easily seen when switching folders in
>>>kmail. While 2.4.21 is instantaneous 2.6.0.test1 shows the clock
>>>for about 2-3 seconds.
>>>
>>>
>
>I see the same problem, and I'm using XFS.  Booting with
>elevator=deadline fixed it for me.  The anticipatory scheduler hurts
>if you have a disc optimised for low power consumption, not speed.
>
>

I don't think this generalisation is really fair. All hard disks
have the same basic properties which AS exploits. There seems to
be something going wrong though.



  parent reply	other threads:[~2003-08-06  0:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05  5:04 Interactive Usage of 2.6.0.test1 worse than 2.4.21 Martin Konold
2003-08-05  5:16 ` William Lee Irwin III
2003-08-05  6:26 ` Andrew Morton
2003-08-05  8:16   ` Oleg Drokin
2003-08-05 22:43   ` Peter Chubb
2003-08-05 23:36     ` Andrew Morton
2003-08-06  0:55     ` Nick Piggin [this message]
2003-08-05  7:23 ` Felipe Alfaro Solana
2003-08-05 12:52 ` Bernd Schubert
2003-08-05 13:37   ` Rahul Karnik
2003-08-05 21:29     ` Martin Konold

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=3F305205.2010705@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.konold@erfrakon.de \
    --cc=peter@chubb.wattle.id.au \
    /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.