From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: massive perf_event slowdown between 4.9 and 4.11-rc
Date: Thu, 16 Mar 2017 19:14:13 +0100 [thread overview]
Message-ID: <20170316181413.kprvdeck3rirexaj@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1703161150070.695@macbook-air>
On Thu, Mar 16, 2017 at 11:54:58AM -0400, Vince Weaver wrote:
> Hello
>
> My student actually noticed this before I did, I was hoping it was some
> sort of error in her data.
>
> Anyway all perf_event functionality (especially reads) has become about
> 20x slower, at least on Intel machines (haswell and skylake are the only
> ones I've tested) sometime between 4.9 and 4.11-rc
>
> For example, in the PAPI tests:
>
> 4.11-rc2
>
> Total cost for PAPI_read (2 counters) over 1000000 iterations
> min cycles : 15192
> max cycles : 3887735
> mean cycles : 15662.057418
> std deviation: 19079.398693
>
>
> 4.9
>
> Total cost for PAPI_read (2 counters) over 1000000 iterations
> min cycles : 864
> max cycles : 78459
> mean cycles : 908.010315
> std deviation: 144.875697
>
>
> The perf_event_test validation tests are also showing this, even when
> using rdpmc() rather than read.
>
> Is there a likely change that might have caused this? Hoping to avoid
> bisecting it as that will kill the rest of the week probably.
No immediate clue; but I can have a poke. Do you have a handy way of
showing this using: perf test rdpmc, or should I hack something
together?
prev parent reply other threads:[~2017-03-16 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 15:54 Vince Weaver
2017-03-16 17:57 ` Vince Weaver
2017-03-16 18:49 ` Peter Zijlstra
2017-03-16 18:14 ` Peter Zijlstra [this message]
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=20170316181413.kprvdeck3rirexaj@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vincent.weaver@maine.edu \
/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®