linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Bagehot <ceeaspb@gmail.com>
To: Mark Davis <markdavisinboston@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Comparing output of two perf cpu profiling reports
Date: Thu, 28 Apr 2016 14:30:50 +0100	[thread overview]
Message-ID: <CAHeneC__nhXwi=+wVwQUsFuCnHWORNJa49ppaVHxUzAVwAVzMQ@mail.gmail.com> (raw)
In-Reply-To: <CAPe7T+9fYXHWa7X4x-su6LujYuOFv7BB7j-jCcdH-hw3oQM9Vw@mail.gmail.com>

Hi Mark,

Differential flame graphs is one way:
http://www.brendangregg.com/blog/2014-11-09/differential-flame-graphs.html

Thanks,
Alex

On Thu, Apr 28, 2016 at 2:27 PM, Mark Davis <markdavisinboston@gmail.com> wrote:
> Hi, what is the recommend way to compare two different perf reports
> from CPU event profiling (via sampling with perf record)? I'm
> comparing two macro benchmarks, with a couple small implementation
> details between the two. Right now I'm manually comparing the output
> of perf report to determine the salient differences. However, I'm
> wondering if there's a tool or otherwise best practice to essentially
> "diff" the two outputs. I could just use diff on the --stdio version
> of the reports, but sometimes lines get mangled and I loose
> context/hierarchy.
>
> Any tips?
>
> Mark
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-28 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 13:27 Comparing output of two perf cpu profiling reports Mark Davis
2016-04-28 13:30 ` Alex Bagehot [this message]
2016-04-28 14:16 ` Arnaldo Carvalho de Melo
2016-04-28 14:17   ` Mark Davis

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='CAHeneC__nhXwi=+wVwQUsFuCnHWORNJa49ppaVHxUzAVwAVzMQ@mail.gmail.com' \
    --to=ceeaspb@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=markdavisinboston@gmail.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;
as well as URLs for NNTP newsgroup(s).