All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Martin Bligh <mbligh@mbligh.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: Performance regression in 2.6.22-git1 (new sched code?)
Date: Tue, 10 Jul 2007 23:09:45 +0200	[thread overview]
Message-ID: <20070710210945.GA4231@elte.hu> (raw)
In-Reply-To: <4693C3D2.9020005@mbligh.org>


* Martin Bligh <mbligh@mbligh.org> wrote:

> ~ 1% on 4-way x86_64
> 
> http://test.kernel.org/perf/kernbench.elm3b6.png
> 
> ~ 4% on 16-way NUMA-Q (i386)
> 
> http://test.kernel.org/perf/kernbench.moe.png
> 
> ~ 1.5% on 4-way i386
> 
> http://test.kernel.org/perf/kernbench.elm3b132.png

thx! I'll check this tomorrow, meanwhile here are a few quick ideas.

1) does reverting this patch improve performance:

   commit 9c4801cebc2add1fe514bc8eb201b16372eee11a
   Author: Ingo Molnar <mingo@elte.hu>
   Date:   Mon Jul 9 18:52:01 2007 +0200

       sched: more agressive idle balancing

2) does changing CONFIG_HZ=250 to CONFIG_HZ=100 improve the numbers? 
   CFS has some internal tuning that depends on HZ - a higher HZ is a 
   sign that the user wants more finegrained scheduling. So for maximum 
   server throughput, use CONFIG_HZ=100.

3) could you turn off CONFIG_SCHED_DEBUG? The cost is small but perhaps 
   measurable.

(these 3 suggestions could be tested together - they should have 
cumulative effects.)

	Ingo

  parent reply	other threads:[~2007-07-10 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 17:37 Performance regression in 2.6.22-git1 (new sched code?) Martin Bligh
2007-07-10 19:20 ` Andy Whitcroft
2007-07-10 21:09 ` Ingo Molnar [this message]
2007-07-11 17: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=20070710210945.GA4231@elte.hu \
    --to=mingo@elte.hu \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.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 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.