From: Andrea Arcangeli <andrea@suse.de>
To: rwhron@earthlink.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: O(1) scheduler gives big boost to tbench 192
Date: Mon, 6 May 2002 18:42:53 +0200 [thread overview]
Message-ID: <20020506184253.B31998@dualathlon.random> (raw)
In-Reply-To: <20020506042005.A18792@rushmore>
On Mon, May 06, 2002 at 04:20:05AM -0400, rwhron@earthlink.net wrote:
> > BTW, Randy, I seen my tree runs slower with tiobench, that's probably
> > because I made the elevator anti-starvation logic more aggressive than
> > mainline and the other kernel trees (to help interactive usage), could
> > you try to run tiobench on -aa after elvtune -r 8192 -w 16384
> > /dev/hd[abcd] to verify? Thanks for the great benchmarking effort.
>
> I will have results on the big machine in a couple days. On the
> small machine, elvtune increases tiobench sequential reads by
> 30-50%, and lowers worst case latency a little.
ok, everything is fine then, thanks for the further benchmarks. Not sure
if I should increase the elvtune defaults, the max latency with 8
reading threads literally doubles (from a mean of 500/600 to 1200). OTOH
with 128 threads max latency even decreases (most probably because of
higher mean throughput).
> > And for the reason fork is faster in -aa that's partly thanks to the
> > reschedule-child-first logic, that can be easily merged in mainline,
> > it's just in 2.5.
>
> Is that part of parent_timeslice patch? parent_timeslice helped
Yep.
> fork a little when I tried to isolating patches to find what
> makes fork faster in -aa. It is more than one patch as far as
> I can tell.
>
> On uniprocessor the unixbench execl test, all -aa kernel's going back
> at least to 2.4.15aa1 are about 20% faster than other trees, even those
> like jam and akpm's splitted vm. Fork in -aa for more "real world"
> test (autoconf build) is about 8-10% over other kernel trees.
>
> On quad Xeon, with bigger L2 cache, autoconf (fork test) the difference
> between mainline and -aa is smaller. The -aa based VMs in aa, jam, and
> mainline have about 15% edge over rmap VM in ac and rmap. jam has a
> slight advantage for autoconf build, possibly because of O(1) effect
> which is more likely to show up since more processes execute
> on the 4 way box.
>
> More quad Xeon at:
> http://home.earthlink.net/~rwhron/kernel/bigbox.html
>
>
> --
> Randy Hron
Andrea
next prev parent reply other threads:[~2002-05-06 16:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 8:20 O(1) scheduler gives big boost to tbench 192 rwhron
2002-05-06 16:42 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 12:46 rwhron
2002-05-08 16:39 Bill Davidsen
2002-05-03 16:37 John Hawkes
2002-05-03 13:38 rwhron
2002-05-03 20:29 ` Gerrit Huizenga
2002-05-04 8:13 ` Andrea Arcangeli
2002-05-07 22:13 ` Mike Kravetz
2002-05-07 22:44 ` Alan Cox
2002-05-07 22:43 ` Mike Kravetz
2002-05-07 23:39 ` Robert Love
2002-05-07 23:48 ` Mike Kravetz
2002-05-08 15:34 ` Jussi Laako
2002-05-08 16:31 ` Robert Love
2002-05-08 17:02 ` Mike Kravetz
2002-05-09 0:26 ` Jussi Laako
2002-05-08 8:50 ` Andrea Arcangeli
2002-05-09 23:18 ` Mike Kravetz
2002-05-02 21:36 rwhron
2002-05-03 0:09 ` Gerrit Huizenga
2002-05-02 23:17 ` J.A. Magallon
2002-05-03 0:14 ` Alan Cox
2002-05-03 1:08 ` Gerrit Huizenga
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=20020506184253.B31998@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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