From: Mike Kravetz <kravetz@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] hackbench: New Multiqueue Scheduler Benchmark
Date: Tue, 11 Dec 2001 09:02:01 -0800 [thread overview]
Message-ID: <20011211090201.A1137@w-mikek2.des.beaverton.ibm.com> (raw)
In-Reply-To: <E16Dh0t-0003yl-00@wagner.rustcorp.com.au>
In-Reply-To: <E16Dh0t-0003yl-00@wagner.rustcorp.com.au>; from rusty@rustcorp.com.au on Tue, Dec 11, 2001 at 06:07:39PM +1100
On Tue, Dec 11, 2001 at 06:07:39PM +1100, Rusty Russell wrote:
> I've cut down the chat benchmark into a version which doesn't
> use threads or semaphores, and called it hackbench:
>
> On a 12-way PPC64:
> 2.4.17-pre7:
> hackbench 50: Time: 851.469 Time: 847.143 Time: 826.868
>
> 2.4.17-pre7-multiqueue-patch:
> hackbench 50: Time: 15.120 Time: 14.766 Time: 15.067
I suspect the reason for the big difference is runqueue lock contention
(as in the original chat benchmark).
It might be interesting to keep the benchmark load the same and
rerun with a varying number of CPUs. My 'guess' is that with the
default scheduler you will see better numbers with less CPUs. When
we were working with chat on an 8-way Intel, we saw benchmark
numbers peak at around 4 CPUs. As you added more than 4 CPUs,
your benchmark numbers got worse. You can see this graphicly at:
http://lse.sourceforge.net/scheduling/ols2001/img54.htm
--
Mike
prev parent reply other threads:[~2001-12-11 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 7:07 Rusty Russell
2001-12-11 17:02 ` Mike Kravetz [this message]
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=20011211090201.A1137@w-mikek2.des.beaverton.ibm.com \
--to=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=rusty@rustcorp.com.au \
/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®