From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Pengfei Yuan <0xcoolypf@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why not build kernel with -O3
Date: Tue, 07 Apr 2015 08:43:15 +0200 [thread overview]
Message-ID: <1428388995.3152.10.camel@gmail.com> (raw)
In-Reply-To: <CACmZjJK8oLLFWBzUZpRTVrTycu8JDfd+hg6bBuxi-a8U6Hk_1A@mail.gmail.com>
On Tue, 2015-04-07 at 11:37 +0800, Pengfei Yuan wrote:
> Hi,
>
> I have conducted some experiments to compare kernels built with -O2
> and -O3. Here are the results:
>
> Application Performance O2 Performance O3 Improvement
> Apache 127814.14 req/s 130321.24 req/s 1.96%
> Nginx 537589.08 req/s 556723.32 req/s 3.56%
> MySQL 70661.38 tx/s 71008.47 tx/s 0.49%
> PostgreSQL 79763.39 tx/s 79535.59 tx/s -0.29%
> Redis 352547.47 op/s 405417.24 op/s 15.0%
> Memcached 844439.14 op/s 845321.79 op/s 0.10%
>
> Geomean: +3.34%
>
> Experiment environment: Linux 3.19.3, GCC 4.9.3 prerelease, Core-i7
> 4770, 32G RAM, 10GbE
>
> LMbench microbenchmark also shows reduction in various latencies, as
> well as increase of throughputs.
Please show multiple run data for all permutations of supported gcc
version/arch ;-)
-Mike
next prev parent reply other threads:[~2015-04-07 6:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 3:37 Why not build kernel with -O3 Pengfei Yuan
2015-04-07 6:43 ` Mike Galbraith [this message]
2015-04-07 7:07 ` Boaz Harrosh
2015-04-07 8:29 ` Mike Galbraith
2015-04-07 7:56 ` Pengfei Yuan
2015-04-07 10:09 ` Mike Galbraith
2015-04-07 18:05 ` Austin S Hemmelgarn
2015-04-08 1:00 ` Pengfei Yuan
2015-04-08 12:06 ` Austin S Hemmelgarn
2015-04-08 12:57 ` One Thousand Gnomes
2015-04-08 13:19 ` Pengfei Yuan
2015-04-08 13:53 ` Austin S Hemmelgarn
2015-04-08 12:19 ` Richard Weinberger
2015-04-08 12:49 ` Austin S Hemmelgarn
2015-04-08 13:16 ` Pengfei Yuan
2015-04-08 13:21 ` Richard Weinberger
2015-04-27 20:37 ` Pavel Machek
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=1428388995.3152.10.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=0xcoolypf@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