From: rwhron@earthlink.net
To: gh@us.ibm.com
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: O(1) scheduler gives big boost to tbench 192
Date: Fri, 3 May 2002 09:38:56 -0400 [thread overview]
Message-ID: <20020503093856.A27263@rushmore> (raw)
> > > Rumor is that on some workloads MQ it outperforms O(1), but it
> > > may be that the latest (post K3?) O(1) is catching up?
Is MQ based on the Davide Libenzi scheduler?
(a version of Davide's scheduler is in the -aa tree).
> > I'd be interested to know what workloads ?
> AIM on large CPU count machines was the most significant I had heard
> about. Haven't measured recently on database load - we made a cut to
> O(1) some time back for simplicity. Supposedly volanomark was doing
> better for a while but again we haven't cut back to MQ in quite a while;
> trying instead to refine O(1). Volanomark is something of a scheduling
> anomaly though - sender/receiver timing on loopback affects scheduling
> decisions and overall throughput in ways that may or may not be consistent
> with real workloads. AIM is probably a better workload for "real life"
> random scheduling testing.
tbench 192 is an anomaly test too. AIM looks like a nice
"mixed" bench. Do you have any scripts for it? I'd like
to use AIM too.
A side effect of O(1) in ac2 and jam6 on the 4 way box is a decrease
in pipe bandwidth and an increase in pipe latency measured by lmbench:
kernel Pipe bandwidth in MB/s - bigger is better
----------------------- ------
2.4.16 383.93
2.4.19-pre3aa2 316.88
2.4.19-pre5 385.56
2.4.19-pre5-aa1 345.93
2.4.19-pre5-aa1-2g-hio 371.87
2.4.19-pre5-aa1-3g-hio 355.97
2.4.19-pre7 462.80
2.4.19-pre7-aa1 382.90
2.4.19-pre7-ac2 85.66
2.4.19-pre7-jam6 66.41
2.4.19-pre7-rl 464.60
2.4.19-pre7-rmap13 453.24
kernel Pipe latency in microseconds - smaller is better
----------------------- -----
2.4.16 12.73
2.4.19-pre3aa2 13.58
2.4.19-pre5 12.98
2.4.19-pre5-aa1 13.46
2.4.19-pre5-aa1-2g-hio 12.83
2.4.19-pre5-aa1-3g-hio 13.08
2.4.19-pre7 10.71
2.4.19-pre7-aa1 13.32
2.4.19-pre7-ac2 31.95
2.4.19-pre7-jam6 29.51
2.4.19-pre7-rl 10.71
2.4.19-pre7-rmap13 10.75
More at:
http://home.earthlink.net/~rwhron/kernel/bigbox.html
--
Randy Hron
next reply other threads:[~2002-05-03 13:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 13:38 rwhron [this message]
2002-05-03 20:29 ` O(1) scheduler gives big boost to tbench 192 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
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 12:46 rwhron
2002-05-08 16:39 Bill Davidsen
2002-05-06 8:20 rwhron
2002-05-06 16:42 ` Andrea Arcangeli
2002-05-03 16:37 John Hawkes
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=20020503093856.A27263@rushmore \
--to=rwhron@earthlink.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gh@us.ibm.com \
--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.