From: Nick Piggin <piggin@cyberone.com.au>
To: Philip Martin <philip@codematters.co.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
Date: Tue, 03 Feb 2004 14:02:55 +1100 [thread overview]
Message-ID: <401F0F5F.10306@cyberone.com.au> (raw)
In-Reply-To: <87isipvuvz.fsf@codematters.co.uk>
Philip Martin wrote:
>Andrew Morton <akpm@osdl.org> writes:
>
>
>>Nick Piggin <piggin@cyberone.com.au> wrote:
>>
>>>Andrew, any other ideas?
>>>
>>There seems to be a lot more writeout happening.
>>
>
>As far as I can see (and hear!) that's true.
>
>
>>You could try setting /proc/sys/vm/dirty_ratio to 60 and
>>/proc/sys/vm/dirty_background_ratio to 40.
>>
>
>Not much different:
>
>2.6.1 (without elevator=deadline)
>
>dirty_ratio:60 dirty_background_ratio:40
>
>245.58user 121.82system 3:31.79elapsed 173%CPU (0avgtext+0avgdata 0maxresident)k
>0inputs+0outputs (0major+3771340minor)pagefaults 0swaps
>
>dirty_ratio:40 dirty_background_ratio:10 (the defaults)
>
>245.75user 121.33system 3:35.13elapsed 170%CPU (0avgtext+0avgdata 0maxresident)k
>0inputs+0outputs (0major+3770826minor)pagefaults 0swaps
>
>
>
OK now thats strange - you're definitely compiling the same kernel
with the same .config and compiler? 2.6 looks like its doing twice
the amount of writeout that 2.4 is.
Can you try the memory pressure program I sent you earlier?
next prev parent reply other threads:[~2004-02-03 3:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 21:34 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs Philip Martin
2004-02-01 23:11 ` Andrew Morton
2004-02-01 23:42 ` Philip Martin
2004-02-01 23:52 ` Nick Piggin
2004-02-02 0:51 ` Philip Martin
2004-02-02 5:15 ` Nick Piggin
2004-02-02 8:58 ` Nick Piggin
2004-02-02 18:36 ` Philip Martin
2004-02-02 23:36 ` Nick Piggin
2004-02-02 23:49 ` Andrew Morton
2004-02-03 1:01 ` Philip Martin
2004-02-03 3:02 ` Nick Piggin [this message]
2004-02-03 16:44 ` Philip Martin
2004-02-03 0:34 ` Philip Martin
2004-02-03 3:52 ` Nick Piggin
2004-02-02 18:08 ` Philip Martin
2004-02-03 3:46 ` Andrew Morton
2004-02-03 16:46 ` Philip Martin
2004-02-03 21:29 ` Andrew Morton
2004-02-03 21:53 ` Philip Martin
2004-02-04 5:48 ` Nick Piggin
2004-02-04 17:50 ` Philip Martin
2004-02-04 23:38 ` Philip Martin
2004-02-05 2:49 ` Nick Piggin
2004-02-05 14:27 ` Philip Martin
2004-02-14 0:10 ` Philip Martin
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 6:55 Samium Gromoff
2004-02-03 7:07 ` Andrew Morton
2004-02-03 7:52 ` Samium Gromoff
2004-02-03 7:57 ` Nick Piggin
2004-02-03 15:58 ` Valdis.Kletnieks
2004-02-03 7:13 ` Nick Piggin
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=401F0F5F.10306@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philip@codematters.co.uk \
/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