From: Michael Hohnbaum <hohnbaum@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Erich Focht <efocht@ess.nec.de>, Robert Love <rml@tech9.net>,
Ingo Molnar <mingo@elte.hu>,
Stephen Hemminger <shemminger@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5.53] NUMA scheduler (1/3)
Date: 05 Jan 2003 19:58:46 -0800 [thread overview]
Message-ID: <1041825533.21653.41.camel@kenai> (raw)
In-Reply-To: <108220000.1041744901@titus>
On Sat, 2003-01-04 at 21:35, Martin J. Bligh wrote:
> >> Here comes the minimal NUMA scheduler built on top of the O(1) load
> >> balancer rediffed for 2.5.53 with some changes in the core part. As
> >> suggested by Michael, I added the cputimes_stat patch, as it is
> >> absolutely needed for understanding the scheduler behavior.
> >
> > Thanks for this latest patch. I've managed to cobble together
> > a 4 node NUMAQ system (16 700 MHZ PIII procs, 16GB memory) and
> > ran kernbench and schedbench on this, along with the 2.5.50 and
> > 2.5.52 versions. Results remain fairly consistent with what
> > we have been obtaining on earlier versions.
> >
> > Kernbench:
> > Elapsed User System CPU
> > sched50 29.96s 288.308s 83.606s 1240.8%
> > sched52 29.836s 285.832s 84.464s 1240.4%
> > sched53 29.364s 284.808s 83.174s 1252.6%
> > stock50 31.074s 303.664s 89.194s 1264.2%
> > stock53 31.204s 306.224s 87.776s 1263.2%
>
> Not sure what you're correllating here because your rows are all named
> the same thing. However, the new version seems to be much slower
> on systime (about 7-8% for me), which roughly correllates with your
> last two rows above. Me no like.
Sorry, I forgot to include a bit better description of what the
row labels mean.
sched50 = linux 2.5.50 with the NUMA scheduler
sched52 = linux 2.5.52 with the NUMA scheduler
sched53 = linux 2.5.53 with the NUMA scheduler
stock50 = linux 2.5.50 without the NUMA scheduler
stock53 = linux 2.5.53 without the NUMA scheduler
Thus, this shows that the NUMA scheduler drops systime by ~5.5 secs,
or roughly 8%. So, my testing is not showing an increase in systime
like you apparently are seeing.
Michael
--
Michael Hohnbaum 503-578-5486
hohnbaum@us.ibm.com T/L 775-5486
next prev parent reply other threads:[~2003-01-06 3:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 16:34 NUMA scheduler BK tree Erich Focht
2002-11-06 18:10 ` Michael Hohnbaum
2002-11-07 23:05 ` Erich Focht
2002-11-07 23:46 ` Michael Hohnbaum
2002-11-08 16:57 ` Erich Focht
2002-11-11 15:13 ` [PATCH 2.5.47] NUMA scheduler (1/2) Erich Focht
2002-11-11 15:14 ` [PATCH 2.5.47] NUMA scheduler (2/2) Erich Focht
2002-11-12 0:24 ` [PATCH 2.5.47] NUMA scheduler (1/2) Michael Hohnbaum
2002-11-18 19:40 ` NUMA scheduler BK tree Martin J. Bligh
2002-11-19 16:26 ` [PATCH 2.5.48] NUMA scheduler (1/2) Erich Focht
2002-11-19 16:27 ` [PATCH 2.5.48] NUMA scheduler (2/2) Erich Focht
2002-12-02 15:29 ` [PATCH 2.5.50] NUMA scheduler (1/2) Erich Focht
2002-12-02 15:30 ` [PATCH 2.5.50] NUMA scheduler (2/2) Erich Focht
2002-12-06 17:39 ` [PATCH 2.5.50] NUMA scheduler (1/2) Michael Hohnbaum
2002-12-18 16:21 ` [PATCH 2.5.52] " Erich Focht
2002-12-18 16:23 ` [PATCH 2.5.52] NUMA scheduler (2/2) Erich Focht
2002-12-20 14:49 ` [PATCH 2.5.52] NUMA scheduler: cputimes stats Erich Focht
2002-12-20 15:17 ` [PATCH 2.5.52] NUMA scheduler (1/2) Christoph Hellwig
2002-12-20 17:44 ` Erich Focht
2002-12-31 13:29 ` [PATCH 2.5.53] NUMA scheduler (1/3) Erich Focht
2002-12-31 13:29 ` [PATCH 2.5.53] NUMA scheduler (2/3) Erich Focht
2002-12-31 13:30 ` [PATCH 2.5.53] NUMA scheduler (3/3) Erich Focht
2003-01-04 1:58 ` [PATCH 2.5.53] NUMA scheduler (1/3) Michael Hohnbaum
2003-01-05 5:35 ` Martin J. Bligh
2003-01-06 3:58 ` Michael Hohnbaum [this message]
2003-01-06 6:07 ` Martin J. Bligh
2003-01-07 2:23 ` Michael Hohnbaum
2003-01-07 11:27 ` Erich Focht
2003-01-07 23:35 ` Michael Hohnbaum
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=1041825533.21653.41.camel@kenai \
--to=hohnbaum@us.ibm.com \
--cc=efocht@ess.nec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--cc=shemminger@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox