From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"Ma, Chinang" <chinang.ma@intel.com>, Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Styner, Douglas W" <douglas.w.styner@intel.com>,
"Chilukuri, Harita" <harita.chilukuri@intel.com>,
"Wang, Peter Xihong" <peter.xihong.wang@intel.com>,
"Nueckel, Hubert" <hubert.nueckel@intel.com>
Subject: Re: CFS scheduler OLTP perforamnce
Date: Fri, 12 Dec 2008 15:39:30 +0100 [thread overview]
Message-ID: <20081212143930.GI25779@one.firstfloor.org> (raw)
In-Reply-To: <1229091735.25485.8.camel@twins>
On Fri, Dec 12, 2008 at 03:22:15PM +0100, Peter Zijlstra wrote:
> On Fri, 2008-12-12 at 15:15 +0100, Andi Kleen wrote:
> > Peter Zijlstra <peterz@infradead.org> writes:
> > >>
> > >> It seems that in this case renice to higher priority with CFS did not
> > >> reduce scheduling latency as well as SCHED_RR.
> > >
> > > Is there a question in this email?
> >
> > The question is how to make nice perform as well as SCHED_RR.
>
> Depending on the circumstances, you can't - SCHED_RR doesn't bother with
> fairness.
When the spread between nice levels (negative/positive) is large enough
at least the log writer should be able to schedule soon most of the
time, no?
At least that doesn't seem to work.
Also in general there seems to be a starvation issue here between
producer and consumer.
-Andi
next prev parent reply other threads:[~2008-12-12 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 23:25 CFS scheduler OLTP perforamnce Ma, Chinang
2008-12-12 12:12 ` Peter Zijlstra
2008-12-12 13:38 ` Peter Zijlstra
2008-12-12 14:04 ` Gilles.Carry
2008-12-12 21:45 ` Ma, Chinang
2008-12-14 14:43 ` Henrik Austad
2008-12-15 15:32 ` Ma, Chinang
2008-12-15 16:57 ` Henrik Austad
2008-12-15 20:49 ` Ma, Chinang
2008-12-12 14:15 ` Andi Kleen
2008-12-12 14:22 ` Peter Zijlstra
2008-12-12 14:39 ` Andi Kleen [this message]
2008-12-12 17:25 ` Ma, Chinang
2008-12-12 12:37 ` Gilles.Carry
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=20081212143930.GI25779@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=arjan.van.de.ven@intel.com \
--cc=chinang.ma@intel.com \
--cc=douglas.w.styner@intel.com \
--cc=harita.chilukuri@intel.com \
--cc=hubert.nueckel@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mingo@elte.hu \
--cc=peter.xihong.wang@intel.com \
--cc=peterz@infradead.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