From: Ingo Molnar <mingo@elte.hu>
To: Colin Fowler <elethiomel@gmail.com>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon
Date: Fri, 18 Jan 2008 11:55:45 +0100 [thread overview]
Message-ID: <20080118105545.GC12228@elte.hu> (raw)
In-Reply-To: <cf3edd8d0801160934u2e39110dv2ccc98081e983b25@mail.gmail.com>
* Colin Fowler <elethiomel@gmail.com> wrote:
> > there are a handful of 'scheduler feature bits' in
> > /proc/sys/kernel/sched_features:
> >
> > enum {
> > SCHED_FEAT_NEW_FAIR_SLEEPERS = 1,
> > SCHED_FEAT_WAKEUP_PREEMPT = 2,
> > SCHED_FEAT_START_DEBIT = 4,
> > SCHED_FEAT_TREE_AVG = 8,
> > SCHED_FEAT_APPROX_AVG = 16,
> > };
> >
>
> Toggling SCHED_FEAT_NEW_FAIR_SLEEPERS to 0 or
> SCHED_FEAT_WAKEUP_PREEMPT to 0 gives me results more inline with my
> 2.6.22 results. Toggling them both to 0 gives me slightly better
> results than 2.6.22!
ok, but it would be nice to avoid having to turn these off. Could you
try whether tuning the /proc/sys/kernel/*granularity* values (in
particular wakeup_granularity) has any positive effect on your workload?
also, could you run your workload as SCHED_BATCH [via schedtool -B ],
does that improve the results as well on a default-tuned kernel?
Ingo
prev parent reply other threads:[~2008-01-18 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 17:37 Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon Colin Fowler
2008-01-14 18:55 ` Ingo Molnar
2008-01-14 22:42 ` Colin Fowler
2008-01-14 22:43 ` Colin Fowler
2008-01-15 17:01 ` Colin Fowler
2008-01-15 22:06 ` Ingo Molnar
2008-01-15 23:05 ` Colin Fowler
2008-01-16 15:35 ` Ingo Molnar
2008-01-16 16:10 ` Colin Fowler
2008-01-16 16:19 ` Ingo Molnar
2008-01-16 16:38 ` Colin Fowler
2008-01-16 17:34 ` Colin Fowler
2008-01-18 10:55 ` Ingo Molnar [this message]
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=20080118105545.GC12228@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=elethiomel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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