From: "Rob Hussey" <robjhussey@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: Scheduler benchmarks - a follow-up
Date: Tue, 18 Sep 2007 00:30:05 -0400 [thread overview]
Message-ID: <6b8cef970709172130v317a6c48h814ef5a1488f798e@mail.gmail.com> (raw)
In-Reply-To: <20070917203607.GA20564@elte.hu>
On 9/17/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > i've meanwhile tested hackbench 90 and the performance difference
> > between -ck and -cfs-devel seems to be mostly down to the more precise
> > (but slower) sched_clock() introduced in v2.6.23 and to the startup
> > penalty of freshly created tasks.
>
> Rob, another thing i just noticed in your .configs: you have
> CONFIG_PREEMPT=y enabled. Would it be possible to get a testrun with
> that disabled? That gives the best throughput and context-switch latency
> numbers. (CONFIG_PREEMPT might also have preemption artifacts - there's
> one report of it having _worse_ desktop latencies on certain hardware
> than !CONFIG_PREEMPT.)
I reverted the patch from before since it didn't seem to help. Do you
think it may have to do with my system having Hyper-Threading enabled?
I should have pointed out before that I don't really have a dual-core
system, just a P4 with Hyper-Threading (I loosely used core to refer
to processor).
Some new numbers for 2.6.23-rc6-cfs-devel (!CONFIG_PREEMPT and bound
to single processor)
lat_ctx:
15 2.73
16 2.74
17 2.81
18 2.74
19 2.74
20 2.73
21 2.60
22 2.74
23 2.72
24 2.74
25 2.74
hackbench:
80 11.578
81 11.991
82 11.914
83 12.026
84 12.226
85 12.347
86 12.552
87 12.655
88 13.011
89 12.941
90 13.237
pipe-test:
1 9.58
2 9.58
3 9.58
4 9.58
5 9.58
6 9.58
7 9.58
8 9.58
9 9.58
10 9.58
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
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.
Regards,
Rob
next prev parent reply other threads:[~2007-09-18 4:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 9:21 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 [this message]
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
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=6b8cef970709172130v317a6c48h814ef5a1488f798e@mail.gmail.com \
--to=robjhussey@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.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 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®