From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Subject: O(1) scheduler gives big boost to tbench 192
Date: Thu, 2 May 2002 17:36:56 -0400 [thread overview]
Message-ID: <20020502173656.A26986@rushmore> (raw)
On an OSDL 4 way x86 box the O(1) scheduler effect
becomes obvious as the run queue gets large.
2.4.19-pre7-ac2 and 2.4.19-pre7-jam6 have the O(1) scheduler.
At 192 processes, O(1) shows about 340% improvement in throughput.
The dyn-sched in -aa appears to be somewhat improved over the
standard scheduler.
Numbers are in MB/second.
tbench 192 processes
2.4.16 29.39
2.4.17 29.70
2.4.19-pre5 29.01
2.4.19-pre5-aa1 29.22
2.4.19-pre5-aa1-2g-hio 29.94
2.4.19-pre5-aa1-3g-hio 28.66
2.4.19-pre7 29.93
2.4.19-pre7-aa1 32.75
2.4.19-pre7-ac2 103.98
2.4.19-pre7-rmap13 29.46
2.4.19-pre7-jam6 104.98
2.4.19-pre7-rl 29.74
At 64 processes, O(1) helps a little. ac2 and jam6 have
the highest numbers here too.
tbench 64 processes
2.4.16 101.99
2.4.17 103.49
2.4.19-pre5-aa1 102.43
2.4.19-pre5-aa1-2g-hio 104.30
2.4.19-pre5-aa1-3g-hio 104.60
2.4.19-pre7 100.86
2.4.19-pre7-aa1 101.76
2.4.19-pre7-ac2 105.89
2.4.19-pre7-rmap13 100.94
2.4.19-pre7-rl 99.65
2.4.19-pre7-jam6 108.23
I've seen some benefit on a uniprocessor box running tbench 32
for kernels with O(1). Hmm, have to try tbench 192 on uniproc
and see if the difference is all scheduler overhead.
I'm putting together a page with more results on this machine.
It will be growing at:
http://home.earthlink.net/~rwhron/kernel/bigbox.html
--
Randy Hron
next reply other threads:[~2002-05-02 21:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 21:36 rwhron [this message]
2002-05-03 0:09 ` O(1) scheduler gives big boost to tbench 192 Gerrit Huizenga
2002-05-02 23:17 ` J.A. Magallon
2002-05-03 0:14 ` Alan Cox
2002-05-03 1:08 ` Gerrit Huizenga
-- strict thread matches above, loose matches on Subject: below --
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-03 16:37 John Hawkes
2002-05-06 8:20 rwhron
2002-05-06 16:42 ` Andrea Arcangeli
2002-05-08 16:39 Bill Davidsen
2002-05-20 12:46 rwhron
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=20020502173656.A26986@rushmore \
--to=rwhron@earthlink.net \
--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 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.