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

Martin Bligh 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
> 
> There's readprofiles and stuff available from here:
> http://test.kernel.org/functional/index.html
> if you drill down under the tests marked "regression", eg.
> http://test.kernel.org/abat/98796/002.kernbench.test/profiling/profile.text

Ok, I've done a crude comparison of a bunch of the jobs we run between
2.6.22 and 2.6.22-git1 kernbench runs, extracting the wallclock, user
and system times for each.  First column is 2.6.22, second is
2.6.22-git1, third is the delta.  +ve bad, -ve good.  Note that I have
hand correlated these jobs so error is possible, but it matches Martin's
figures I belive.

bl6-13
	User    85.14  88.53   3.99
	System  34.16  34.71   1.60
	Total  119.30 123.24   3.30
elm3b132
	User   2397.82 2431.95   1.42
	System 207.41 206.78  -0.30
	Total  2605.23 2638.73   1.29
elm3b6
	User   352.18 357.18   1.42
	System  37.06  36.61  -1.22
	Total  389.24 393.79   1.17
oia5-hs20
	User   645.02 653.47   1.31
	System  49.30  52.45   6.37
	Total  694.33 705.92   1.67
elm3b239
	User   878.21 950.80   8.27
	System 416.06 348.76 -16.18
	Total  1294.27 1299.56   0.41

-apw

  reply	other threads:[~2007-07-10 19:20 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 [this message]
2007-07-10 21:09 ` Ingo Molnar
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=4693DC0C.3050305@shadowen.org \
    --to=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --cc=mingo@elte.hu \
    /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.