From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Eric Farman <farman@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Rik van Riel" <riel@redhat.com>, 王金浦 <jinpuwang@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"KVM-ML (kvm@vger.kernel.org)" <kvm@vger.kernel.org>,
vcaputo@pengaru.com,
"Matthew Rosato" <mjrosato@linux.vnet.ibm.com>
Subject: Re: sysbench throughput degradation in 4.13+
Date: Thu, 28 Sep 2017 11:08:49 +0200 [thread overview]
Message-ID: <9cc35458-cbd8-40a1-584e-2ee61fb9543c@de.ibm.com> (raw)
In-Reply-To: <c47155ca-0e51-0060-c8c2-11588a850a06@linux.vnet.ibm.com>
On 09/27/2017 06:27 PM, Eric Farman wrote:
>
>
> On 09/27/2017 05:35 AM, Peter Zijlstra wrote:
>> On Fri, Sep 22, 2017 at 12:12:45PM -0400, Eric Farman wrote:
>>>
>>> MySQL. We've tried a few different configs with both test=oltp and
>>> test=threads, but both show the same behavior. What I have settled on for
>>> my repro is the following:
>>>
>>
>> Right, didn't even need to run it in a guest to observe a regression.
>>
>> So the below cures native sysbench and NAS bench for me, does it also
>> work for you virt thingy?
[...]
> --test=oltp
> Baseline: 5655.26 transactions/second
> Patched: 9618.13 transactions/second
>
> --test=threads
> Baseline: 25482.9 events/sec
> Patched: 29577.9 events/sec
>
> That's good! With that...
>
> Tested-by: Eric Farman <farman@linux.vnet.ibm.com>
>
> Thanks!
>
> - Eric
Assuming that we settle on this or Riks alternative patch.
Are we going to schedule this for 4.13 stable as well?
next prev parent reply other threads:[~2017-09-28 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 14:14 Eric Farman
2017-09-13 8:24 ` 王金浦
2017-09-22 15:03 ` Eric Farman
2017-09-22 15:53 ` Peter Zijlstra
2017-09-22 16:12 ` Eric Farman
2017-09-27 9:35 ` Peter Zijlstra
2017-09-27 16:27 ` Eric Farman
2017-09-28 9:08 ` Christian Borntraeger [this message]
2017-09-27 17:58 ` Rik van Riel
2017-09-28 11:04 ` Eric Farman
2017-09-28 12:36 ` Peter Zijlstra
2017-09-28 12:37 ` Peter Zijlstra
2017-10-02 22:53 ` Matt Fleming
2017-10-03 8:39 ` Peter Zijlstra
2017-10-03 16:02 ` Rik van Riel
2017-10-04 16:18 ` Peter Zijlstra
2017-10-04 18:02 ` Rik van Riel
2017-10-06 10:36 ` Matt Fleming
2017-10-10 14:51 ` Matt Fleming
2017-10-10 15:16 ` Peter Zijlstra
2017-10-10 17:26 ` Ingo Molnar
2017-10-10 17:40 ` Christian Borntraeger
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=9cc35458-cbd8-40a1-584e-2ee61fb9543c@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=farman@linux.vnet.ibm.com \
--cc=jinpuwang@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=vcaputo@pengaru.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
all inboxes | Powered by JetHome®