From: "Gilles.Carry" <Gilles.Carry@ext.bull.net>
To: "Ma, Chinang" <chinang.ma@intel.com>
Cc: 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 13:37:30 +0100 [thread overview]
Message-ID: <49425B0A.9090808@ext.bull.net> (raw)
In-Reply-To: <BC02C49EEB98354DBA7F5DD76F2A9E80030A74A5FF@azsmsx501.amr.corp.intel.com>
Ma, Chinang a écrit :
> We are evaluating the CFS OLTP performance with 2.6.28-c7 kernel. In this workload once a database foreground process commit a transaction it will signal the log writer process to write to the log file. Foreground processes will wait until log writer finish writing and wake them up. With hundreds of foreground process running in the system, it is important that the log writer get to run as soon as data is available.
>
> Here are the experiments we have done with 2.6.28-rc7.
> 1. Increase log writer priority "renice -20 <log writer pid>" while keeping all other processes running in default CFS priority. We get a baseline performance with log latency (scheduling + i/o) at 7 ms.
>
> 2. To reduce log latency, we set log writer to SCHED_RR with higher priority. We tried "chrt -p 49 <log writer pid>" and got 0.7% boost in performance with log latency reduced to 6.4 ms.
>
> It seems that in this case renice to higher priority with CFS did not reduce scheduling latency as well as SCHED_RR.
Maybe you should try an RT kernel.
Gilles.
prev parent reply other threads:[~2008-12-12 12:37 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
2008-12-12 17:25 ` Ma, Chinang
2008-12-12 12:37 ` Gilles.Carry [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=49425B0A.9090808@ext.bull.net \
--to=gilles.carry@ext.bull.net \
--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 \
/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