public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Rob Hussey <robjhussey@gmail.com>
Cc: linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: Scheduler benchmarks - a follow-up
Date: Tue, 18 Sep 2007 08:40:46 +0200	[thread overview]
Message-ID: <20070918064046.GD5138@elte.hu> (raw)
In-Reply-To: <6b8cef970709172130v317a6c48h814ef5a1488f798e@mail.gmail.com>


* Rob Hussey <robjhussey@gmail.com> wrote:

> A cursory glance suggests that performance wrt lat_ctx and hackbench 
> has increased (lower numbers), but degraded quite a lot for pipe-test. 
> The numbers for pipe-test are extremely stable though, while the 
> numbers for hackbench are more erratic (which isn't saying much since 
> the original numbers gave nearly a straight line). I'm still willing 
> to try out any more ideas.

pipe-test is a very stable workload, and is thus quite sensitive to the 
associativity of the CPU cache. Even killing the task and repeating the 
same test isnt enough to get rid of the systematic skew that this can 
cause. I've seen divergence of up to 10% in pipe-test. One way to test 
it is to run pipe-test, then to stop it, then to "ssh localhost" (this 
in itself uses up a couple of pipe objects and file objects and changes 
the cache layout picture), then run pipe-test again, then again "ssh 
localhost", etc. Via this trick one can often see cache-layout 
artifacts. How much 'skew' does pipe-test have on your system if you try 
this manually?

	Ingo

  parent reply	other threads:[~2007-09-18  6:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17  9:21 Scheduler benchmarks - a follow-up Rob Hussey
2007-09-17 11:12 ` Ed Tomlinson
2007-09-17 11:47   ` Ingo Molnar
2007-09-17 20:22   ` Ingo Molnar
2007-09-17 11:27 ` Ingo Molnar
     [not found]   ` <E1IXMXf-0000uG-ID@flower>
2007-09-17 19:43     ` Willy Tarreau
2007-09-17 20:01       ` Ingo Molnar
2007-09-17 20:06       ` Oleg Verych
2007-09-17 20:05         ` Ingo Molnar
2007-09-17 20:42         ` Willy Tarreau
2007-09-17 13:05 ` Ingo Molnar
2007-09-17 14:01   ` [ck] " Jos Poortvliet
2007-09-17 14:12     ` Ingo Molnar
2007-09-17 20:36   ` Ingo Molnar
2007-09-18  4:30     ` Rob Hussey
2007-09-18  4:53       ` Willy Tarreau
2007-09-18  4:58         ` Rob Hussey
2007-09-18  6:40       ` Ingo Molnar [this message]
2007-09-18  8:23         ` Rob Hussey
2007-09-18  8:48       ` Ingo Molnar
2007-09-18  9:45         ` Rob Hussey
2007-09-18  9:48           ` Ingo Molnar
2007-09-18  1:44   ` Rob Hussey

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=20070918064046.GD5138@elte.hu \
    --to=mingo@elte.hu \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robjhussey@gmail.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