From: Rusty Russell <rusty@rustcorp.com.au>
To: Ryan Cumming <bodnar42@phalynx.dhs.org>
Cc: akeys@post.cis.smu.edu, partha@us.ibm.com,
linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: Performance Results for Ingo's O(1)-scheduler
Date: Tue, 22 Jan 2002 15:45:49 +1100 [thread overview]
Message-ID: <20020122154549.7decbeb9.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200201212016.29055.bodnar42@phalynx.dhs.org>
In-Reply-To: <OF4544D2BC.16B7A12D-ON85256B48.00817250@raleigh.ibm.com> <20020122035540.ZUVU10199.rwcrmhc53.attbi.com@there> <200201212016.29055.bodnar42@phalynx.dhs.org>
On Mon, 21 Jan 2002 20:16:28 -0800
Ryan Cumming <bodnar42@phalynx.dhs.org> wrote:
> On January 21, 2002 19:55, Adam Keys wrote:
> > I'm curious about the performance of the 4-way and 8-way systems. I know
> > nothing about this benchmark. IIRC correctly it simulates chat clients
> > connecting to a server and talking to each other. Is it a CPU, memory, or
> > disk bound benchmark? What is causing the 4-way machines to be only 2x the
> > performance of the 1-way machine and the 8-way machines to be < 3x the
> > performance? Is the system bus the limiting factor on those machines?
>
> Memory bus, lock contention, syncronization issues. SMP really isn't as
> magical as people think after the overhead is taken in to account.
Volcanomark is a Java(TM) chatroom benchmark: multiple rooms, where for each
room, every input from a client generates a write to every other client
(think broadcast storm).
chat (which is a C version of Volcanomark) is useful for testing, as is
hackbench2 (which is cut down to just exhibit the runqueue problem, and
doesn't even use threads).
Hope that helps,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-01-22 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 0:03 Performance Results for Ingo's O(1)-scheduler Partha Narayanan
2002-01-22 3:55 ` Adam Keys
2002-01-22 4:16 ` Ryan Cumming
2002-01-22 4:45 ` Rusty Russell [this message]
2002-01-22 5:28 ` Mark Hahn
[not found] <OF4544D2BC.16B7A12D-ON85256B48.00817250@raleigh.ibm.com >
2002-01-22 2:07 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 5:34 Dieter Nützel
[not found] <20020122053444.A30EE6DA96@mail.elte.hu>
2002-01-22 11:47 ` Ingo Molnar
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=20020122154549.7decbeb9.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akeys@post.cis.smu.edu \
--cc=bodnar42@phalynx.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=partha@us.ibm.com \
/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.