From: Cliff White <cliffw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reaim - 2.6.3-mm1 IO performance down.
Date: Wed, 25 Feb 2004 09:40:55 -0800 [thread overview]
Message-ID: <200402251740.i1PHetn27447@mail.osdl.org> (raw)
In-Reply-To: Your message of "Tue, 24 Feb 2004 17:03:37 PST." <20040224170337.798f5766.akpm@osdl.org>
> cliff white <cliffw@osdl.org> wrote:
> >
> > For the same test on the same machine, results from 2.6.2-rc1-mm2 and 2.6.2
> -rc3-mm1
> > were within 1.0% of the linux-2.6.2 runs. So this is new.
> >
> > More data and tests if requested - are there some patch sets we should try
> reverting?
>
> Thanks. You could try reverting adaptive-lazy-readahead.patch. If it is
> not that I'd be suspecting CPU scheduler changes. Do you have uniprocessor
> test results?
I have them for 2.6.3-mm3, am re-running 2.6.3-mm1 right now.
Gross results are within 1%, but looking at the detail, i do see badness,
example:
Kernel Users Run time
2.6.3 20 32.11
2.6.3-mm3 20 35.47
2.6.3 40 63.64
2.6.3-mm2 40 66.33
Again, this shows up best on the bottom graph on the page.
Graphn of 2.6.3 vs 2.6.3-mm3 :
http://developer.osdl.org/cliffw/reaim/compares/r_comp/2.6.3_vs_mm1_1cpu/index.html
cliffw
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-02-25 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 0:20 cliff white
2004-02-25 1:03 ` Andrew Morton
2004-02-25 17:40 ` Cliff White [this message]
2004-02-25 19:16 ` Andrew Morton
2004-02-25 20:52 ` Cliff White
2004-02-25 23:36 ` Cliff White
2004-02-25 2:00 Con Kolivas
2004-02-25 3:31 ` 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=200402251740.i1PHetn27447@mail.osdl.org \
--to=cliffw@osdl.org \
--cc=akpm@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
all inboxes | Powered by JetHome®