mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <piggin@cyberone.com.au>,
	lkml <linux-kernel@vger.kernel.org>,
	Matt Dobson <colpatch@us.ibm.com>,
	Martin J Bligh <mbligh@aracnet.com>,
	Rick Lindsley <ricklind@us.ibm.com>
Subject: Re: [patch] scheduler: active_load_balance fixes
Date: Mon, 25 Oct 2004 15:37:29 -0700	[thread overview]
Message-ID: <1098743849.23374.44.camel@farah.beaverton.ibm.com> (raw)
In-Reply-To: <20041024023709.2e99cb6d.akpm@osdl.org>

On Sun, 2004-10-24 at 02:37 -0700, Andrew Morton wrote:
> Nick Piggin <piggin@cyberone.com.au> wrote:
> >
> > 
> > 
> > Darren Hart wrote:
> > 
> > >The following patch against the latest mm fixes several problems with
> > >active_load_balance().
> > >
> > >
> > 
> > This seems much better. Andrew can you put this into -mm please.
> > 
> 
> Whenever we touch the load balancing we get sad little reports about
> performance regressions two months later.  How do we gain confidence in
> this change?
> 

I ran kernbench and specjbb on a 16 way xeon ht numa machine (32 total
sibling CPUs) and an 8 way ppc64 machine against 2.6.9-mm1 w/ and w/o my
active_load_balance() patch.  Kernbench was marginally faster on each
machine, and specjbb performed better on 64% of the tests.  SpecJBB is a
bit erratic anyway, so I feel good about these numbers.


Kernbench results below. (2.6.9-mm1-ab is the run with the
active_load_balance patch).

32 way xeon 
2.6.9-mm1
	Elapsed: 81.444s User: 1044.06s System: 138.008s CPU: 1451.2%
2.6.9-mm1-ab
	Elapsed: 81.372s User: 1037.842s System: 139.134s CPU: 1446%

8 way ppc64
2.6.9-mm1
	Elapsed: 53.336s User: 352.932s System: 45.302s CPU: 746%
2.6.9-mm1-ab
	Elapsed: 53.24s User: 353.096s System: 44.98s CPU: 747%

-- 
Darren Hart
IBM, Linux Technology Center
503 578 3185
dvhltc@us.ibm.com

  parent reply	other threads:[~2004-10-26  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 23:36 Darren Hart
2004-10-23  5:30 ` Nick Piggin
2004-10-24  9:37   ` Andrew Morton
2004-10-25 16:58     ` Darren Hart
2004-10-25 22:37     ` Darren Hart [this message]
2004-10-23 10:20 ` 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=1098743849.23374.44.camel@farah.beaverton.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=piggin@cyberone.com.au \
    --cc=ricklind@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 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®