From: Con Kolivas <kernel@kolivas.org>
To: linux-kernel@vger.kernel.org
Cc: Cliff White <cliffw@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: reaim - 2.6.3-mm1 IO performance down.
Date: Wed, 25 Feb 2004 13:00:58 +1100 [thread overview]
Message-ID: <1077674458.403c01da445ea@vds.kolivas.org> (raw)
>Running the reaim 'new_fserver' workload, we now see a performance drop on
>2.6.3-mm1, ext3 filesystem
I observed a serious slowdown on non numa, non smt machines with kernbench and
the scheduler changes (posted results a week ago here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107719112225482&w=2 )
A summary of those results is half job load (-j4 on 8x):
2.6.3: Elapsed Time 231.274
2.6.3-mm1: Elapsed Time 273.688
The drop in reaim performance is possibly related.
Con
next reply other threads:[~2004-02-25 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 2:00 Con Kolivas [this message]
2004-02-25 3:31 ` reaim - 2.6.3-mm1 IO performance down Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 0:20 cliff white
2004-02-25 1:03 ` Andrew Morton
2004-02-25 17:40 ` Cliff White
2004-02-25 19:16 ` Andrew Morton
2004-02-25 20:52 ` Cliff White
2004-02-25 23:36 ` Cliff White
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=1077674458.403c01da445ea@vds.kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=cliffw@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox