All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, John Hawkes <hawkes@sgi.com>
Subject: [PATCH][CFT] NUMA / SMP scheduler "improvements"
Date: Sat, 22 Nov 2003 18:14:23 +1100	[thread overview]
Message-ID: <3FBF0CCF.7060401@cyberone.com.au> (raw)

Hi everyone,
I would like people to test my scheduler improvements if possible,
if you are interested in that sort of thing. Patch at:
http://www.kerneltrap.org/~npiggin/w22/

For those following my patches, the big thing in this release is
balancing backoff needed for the bigger boxes. I'm not sure how
this compares to your stuff John, and it probably isn't tuned too
well for all sizes of boxes.

I use a log(num_online_cpus()) function to scale the global balancing
interval, so this might not be appropriate. It also probably doesn't
do global balances quite enough for 1CPU/node boxes.

Benchmarks are generally as good or better, although idle time may
be up due to more conservative balancing and the backoff stuff.

The good metric is the number of tasks being pulled to another node
dbench pulls    72%
tbench pulls     0.28%
make -j         11.7%
hackbench       17%
reaim           56%

Number of local tasks pulled off CPU is generally down too
dbench    44%
tbench    71%
make -j   76%
hackbench 114%
reaim     100%

This is on osdl's 16 way NUMA (4x4). Testing on other platforms welcome.

Best regards,
Nick


             reply	other threads:[~2003-11-22  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22  7:14 Nick Piggin [this message]
2003-11-22  7:43 ` [PATCH][CFT] NUMA / SMP scheduler "improvements" Nick Piggin

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=3FBF0CCF.7060401@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=hawkes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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.