From: Andres Freund <andres@anarazel.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.15-rc6
Date: Tue, 2 Jan 2018 12:28:59 -0800 [thread overview]
Message-ID: <20180102202859.4fvvrtngnitwzfym@alap3.anarazel.de> (raw)
In-Reply-To: <CA+55aFzU_Q04CVEABo50x24yeTaP-yzzrB1wTPeOiOgAbSKiDA@mail.gmail.com>
On 2017-12-31 14:57:51 -0800, Linus Torvalds wrote:
> With all the x86 pti work coming in late in the rc like this, I'm by
> now almost guaranteed to do an rc8 this release, not because there are
> any known problems, but simply because of the timing of the patches.
>
> Go forth and test,
I thought it'd be interesting to run a short benchmark to be able to
estimate the impact of the PTI work on postgres workloads (which I work
on). On my skylake laptop, a memory resident, OLTP workload with 16
connections results in:
pti=on:
tps = 220791.228297 (including connections establishing)
tps = 220836.842052 (excluding connections establishing)
pti=off:
tps = 236629.778328 (including connections establishing)
tps = 236646.598274 (excluding connections establishing)
model name : Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
This isn't a complaint, I just thought it might be useful
information. If it helps for anything/anybody, I'm happy to run
additional benchmarks / provide additional information.
- Andres
next prev parent reply other threads:[~2018-01-02 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 22:57 Linus Torvalds
2018-01-02 20:28 ` Andres Freund [this message]
2018-01-02 21:09 ` Linus Torvalds
2018-01-03 12:57 ` Willy Tarreau
2018-01-03 21:20 ` Andres Freund
2018-01-04 10:27 ` Willy Tarreau
2018-01-04 11:03 ` Willy Tarreau
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=20180102202859.4fvvrtngnitwzfym@alap3.anarazel.de \
--to=andres@anarazel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®