All of lore.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 11:48:29 +0200	[thread overview]
Message-ID: <20070918094829.GA3809@elte.hu> (raw)
In-Reply-To: <6b8cef970709180245r86d370q2b1a92a29128f2e@mail.gmail.com>


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

> On 9/18/07, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Rob Hussey <robjhussey@gmail.com> wrote:
> >
> > > The obligatory graphs:
> > > http://www.healthcarelinen.com/misc/benchmarks/BOUND_NOPREEMPT_lat_ctx_benchmark.png
> > > http://www.healthcarelinen.com/misc/benchmarks/BOUND_NOPREEMPT_hackbench_benchmark.png
> > > http://www.healthcarelinen.com/misc/benchmarks/BOUND_NOPREEMPT_pipe-test_benchmark.png
> >
> > btw., it's likely that if you turn off CONFIG_PREEMPT for .21 and for
> > .22-ck1 they'll improve a bit too - so it's not fair to put the .23
> > !PREEMPT numbers on the graph as the PREEMPT numbers of the other
> > kernels. (it shows the .23 scheduler being faster than it really is)
> >
> 
> The graphs are really just to show where the new numbers fit in. Plus, 
> I was too lazy to run all the numbers again.

yeah - the graphs are completely OK (and they are really nice and 
useful), i just wanted to point this out for completeness.

> > the pipe-test behavior looks like an outlier. !PREEMPT only removes 
> > code (which makes the code faster), so this could be a cache layout 
> > artifact. (or perhaps we preempt at a different point which is 
> > disadvantageous to caching?) Pipe-test is equivalent to "lat_ctx -s 
> > 0 2" so if there was a genuine slowdown it would show up in the 
> > lat_ctx graph - but the graph shows a speedup.
> 
> Interestingly, every set of lat_ctx -s 0 2 numbers I run on the 
> !PREEMPT kernel are on average higher than with PREEMPT (around 2.84 
> for !PREEMPT and 2.4 for PREEMPT). Anything higher than around 2 or 3 
> (such as lat_ctx -s 0 8) gives lower average numbers for !PREEMPT.

perhaps this 2 task ping-pong is somehow special in that it manages to 
fit into L1 cache much better under PREEMPT than under !PREEMPT. 
(usually the opposite is true) At 3 tasks or more things dont fit 
anymore (or the special alignment is gone) so the faster !PREEMPT code 
wins.

	Ingo

  reply	other threads:[~2007-09-18  9:49 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
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 [this message]
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=20070918094829.GA3809@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 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.