From: Peter Zijlstra <peterz@infradead.org>
To: Eric Farman <farman@linux.vnet.ibm.com>
Cc: "Rik van Riel" <riel@redhat.com>, 王金浦 <jinpuwang@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Christian Borntraeger" <borntraeger@de.ibm.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: Fri, 22 Sep 2017 17:53:48 +0200 [thread overview]
Message-ID: <20170922155348.zujigkn3o5eylctn@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <50a279d3-84eb-3403-f2f0-854934778037@linux.vnet.ibm.com>
On Fri, Sep 22, 2017 at 11:03:39AM -0400, Eric Farman wrote:
> Hi Peter, Rik,
>
> With OSS last week, I'm sure this got lost in the deluge, so here's a
> friendly ping.
Very much so, inbox is a giant trainwreck ;-)
> I picked up 4.14.0-rc1 earlier this week, and still see the
> degradation described above. Not really a surprise, since I don't see any
> other commits in this area beyond the ones I mentioned in my original note.
>
> Anyway, I'm unsure what else to try or what doc to pull to help debug this,
> and would appreciate your expertise here. We can repro this pretty easily
> as necessary to help get to the bottom of this.
>
> Many thanks in advance,
Could you describe your sysbench setup? Are you running it on mysql or
postgresql, what other options?
next prev parent reply other threads:[~2017-09-22 15:53 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 [this message]
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
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=20170922155348.zujigkn3o5eylctn@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=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=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®