From: Andreas Bluemle <andreas.bluemle@itxperts.de>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: 10/7/2014 Weekly Ceph Performance Meeting: kernel boot params
Date: Wed, 8 Oct 2014 18:32:34 +0200 [thread overview]
Message-ID: <20141008183234.19a24ac1@doppio> (raw)
In-Reply-To: <54348A89.1060906@redhat.com>
Hi,
as mentioned during today's meeting, here are the kernel
boot parameters which I found to provide the basis for
good performance results:
processor.max_cstate=0
intel_idle.max_cstate=0
I understand these to basically turn off any power saving modes
of the CPU; the CPU's we are using are like
Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz
Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz
At the BIOS level, we
- turn off Hyperthraeding
- turn off Turbo mode (in order ot not leave the specifications)
- turn on frequency floor override
We also assert that
/sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
is set to "performance"
Using above we see a constant frequency at the maximum level
allowed by the CPU (except Turbo mode).
Best Regards
Andreas Bluemle
On Wed, 8 Oct 2014 02:51:21 +0200
Mark Nelson <mark.nelson@inktank.com> wrote:
> Hi All,
>
> Just a remind that the weekly performance meeting is on Wednesdays at
> 8AM PST. Same bat time, same bat channel!
>
> Etherpad URL:
> http://pad.ceph.com/p/performance_weekly
>
> To join the Meeting:
> https://bluejeans.com/268261044
>
> To join via Browser:
> https://bluejeans.com/268261044/browser
>
> To join with Lync:
> https://bluejeans.com/268261044/lync
>
>
> To join via Room System:
> Video Conferencing System: bjn.vc -or- 199.48.152.152
> Meeting ID: 268261044
>
> To join via Phone:
> 1) Dial:
> +1 408 740 7256
> +1 888 240 2560(US Toll Free)
> +1 408 317 9253(Alternate Number)
> (see all numbers - http://bluejeans.com/numbers)
> 2) Enter Conference ID: 268261044
>
> Mark
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Andreas Bluemle mailto:Andreas.Bluemle@itxperts.de
ITXperts GmbH http://www.itxperts.de
Balanstrasse 73, Geb. 08 Phone: (+49) 89 89044917
D-81541 Muenchen (Germany) Fax: (+49) 89 89044910
Company details: http://www.itxperts.de/imprint.htm
next prev parent reply other threads:[~2014-10-08 16:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 0:51 10/7/2014 Weekly Ceph Performance Meeting Mark Nelson
2014-10-08 16:32 ` Andreas Bluemle [this message]
2014-10-08 17:38 ` 10/7/2014 Weekly Ceph Performance Meeting: kernel boot params Somnath Roy
2014-10-08 17:47 ` Duan, Jiangang
2014-10-08 17:53 ` Somnath Roy
2014-10-08 20:03 ` Duan, Jiangang
2014-10-09 0:50 ` Somnath Roy
2014-10-09 1:07 ` Mark Nelson
2014-10-09 6:45 ` Somnath Roy
2014-10-10 23:39 ` Duan, Jiangang
2014-10-10 23:43 ` Somnath Roy
2014-11-05 14:33 ` Zhang, Jian
2014-10-08 17:57 ` Loic Dachary
2014-10-08 18:07 ` Alexandre DERUMIER
2014-10-08 18:35 ` Stefan Priebe
2014-10-08 23:55 ` Paul Von-Stamwitz
2014-10-14 11:22 ` Andreas Bluemle
2014-10-14 13:13 ` Sage Weil
2014-10-14 14:38 ` Andreas Bluemle
[not found] ` <75674D092A819E4189E91166C74CB90D0144A660@shsmsx102.ccr.corp.intel.com>
2014-10-15 2:23 ` Sage Weil
2014-10-15 2:43 ` Somnath Roy
2014-10-15 2:59 ` Shu, Xinxin
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=20141008183234.19a24ac1@doppio \
--to=andreas.bluemle@itxperts.de \
--cc=ceph-devel@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