From: "Jos Poortvliet" <jospoortvliet@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Rob Hussey" <robjhussey@gmail.com>,
ck@vds.kolivas.org, linux-kernel@vger.kernel.org
Subject: Re: [ck] Re: Scheduler benchmarks - a follow-up
Date: Mon, 17 Sep 2007 16:01:31 +0200 [thread overview]
Message-ID: <5c77e14b0709170701q2835669fu4d18b6734bcc5119@mail.gmail.com> (raw)
In-Reply-To: <20070917130524.GA10707@elte.hu>
On 9/17/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Rob Hussey <robjhussey@gmail.com> wrote:
>
> > http://www.healthcarelinen.com/misc/benchmarks/BOUND_hackbench_benchmark2.png
>
> heh - am i the only one impressed by the consistency of the blue line in
> this graph? :-) [ and the green line looks a bit like a .. staircase? ]
Looks lovely, though as long as lower is better, that staircase does a
nice job ;-)
> 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.
>
> Putting back the 2.6.22 version and tweaking the startup penalty gives
> this:
>
> [hackbench 90, smaller is better]
>
> sched-devel.git sched-devel.git+lowres-sched-clock+dsp
> --------------- --------------------------------------
> 5.555 5.149
> 5.641 5.149
> 5.572 5.171
> 5.583 5.155
> 5.532 5.111
> 5.540 5.138
> 5.617 5.176
> 5.542 5.119
> 5.587 5.159
> 5.553 5.177
> --------------------------------------
> avg: 5.572 avg: 5.150 (-8.1%)
Hmmm. So cfs was 0.8% slower compared to ck in the test by Rob, it
became 8% faster so... it should be faster than CK - provided these
results are valid over different tests.
But this is all microbenchmarks, which won't have much effect in real
life, right? Besides, will the lowres sched clock patch get in?
> ('lowres-sched-clock' is the patch i sent in the previous mail. 'dsp' is
> a disable-startup-penalty patch that is in the latest sched-devel.git)
>
> i have used your .config to conduct this test.
>
> can you reproduce this with the (very-) latest sched-devel git tree:
>
> git-pull git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched-devel.git
>
> plus with the low-res-sched-clock patch (re-) attached below?
>
> Ingo
> ---
> arch/i386/kernel/tsc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux/arch/i386/kernel/tsc.c
> ===================================================================
> --- linux.orig/arch/i386/kernel/tsc.c
> +++ linux/arch/i386/kernel/tsc.c
> @@ -110,9 +110,9 @@ unsigned long long native_sched_clock(vo
> * very important for it to be as fast as the platform
> * can achive it. )
> */
> - if (unlikely(!tsc_enabled && !tsc_unstable))
> + if (1 || unlikely(!tsc_enabled && !tsc_unstable))
> /* No locking but a rare wrong value is not a big deal: */
> - return (jiffies_64 - INITIAL_JIFFIES) * (1000000000 / HZ);
> + return jiffies_64 * (1000000000 / HZ);
>
> /* read the Time Stamp Counter: */
> rdtscll(this_offset);
> _______________________________________________
> http://ck.kolivas.org/faqs/replying-to-mailing-list.txt
> ck mailing list - mailto: ck@vds.kolivas.org
> http://vds.kolivas.org/mailman/listinfo/ck
>
next prev parent reply other threads:[~2007-09-17 14:01 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 ` Jos Poortvliet [this message]
2007-09-17 14:12 ` [ck] " 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
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=5c77e14b0709170701q2835669fu4d18b6734bcc5119@mail.gmail.com \
--to=jospoortvliet@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®