From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
Jean Pihet <jean.pihet@linaro.org>, Arun Sharma <asharma@fb.com>
Subject: Re: [PATCH 2/2] perf callchain: Use global caching provided by libunwind
Date: Wed, 24 Sep 2014 10:04:43 +0900 [thread overview]
Message-ID: <878ul9ltg4.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CAM9d7cgwSrqLNghb3Vdt-=c9w1iFq0wc-njVP4UxkWD4hXCteg@mail.gmail.com> (Namhyung Kim's message of "Tue, 23 Sep 2014 21:53:43 +0900")
On Tue, 23 Sep 2014 21:53:43 +0900, Namhyung Kim wrote:
> On Tue, Sep 23, 2014 at 9:28 PM, Jiri Olsa <jolsa@redhat.com> wrote:
>> On Tue, Sep 23, 2014 at 03:30:28PM +0900, Namhyung Kim wrote:
>>> The libunwind provides two caching policy which are global and
>>> per-thread. As perf unwinds callchains in a single thread, it'd
>>> sufficient to use global caching.
>>>
>>> This speeds up my perf report from 14s to 7s on a ~260MB data file.
>>> Although the output contains a slight difference (~0.01% in terms of
>>> number of lines printed) on callchains which were not resolved.
>>
>> hum, the speedup is nice, but what was the diff output.. any example?
>> The new version does not print some lines or different ones?
>
> I don't have the result now - will post the diff when I go to the
> office tomorrow. But IIRC new version only adds new lines..
Okay, this is the result.. But it doesn't always make a difference. I
can see it produces exactly same output for other (even bigger) data files.
$ diff -U0 callchain-result.{old,new}
--- callchain-result.old 2014-09-23 14:52:29.630711402 +0900
+++ callchain-result.new 2014-09-23 14:52:52.709505500 +0900
@@ -5322,0 +5323,9 @@
+ | | |
+ | | --0.00%-- 0x406520
+ | | 0x4064f0
+ | | |
+ | | |--0.00%-- 0x1ad52a0
+ | | |
+ | | |--0.00%-- 0x1a0f2e0
+ | | |
+ | | --0.00%-- 0x1a9e0c0
@@ -108899,0 +108909,3 @@
+ | | 0x406520
+ | | 0x4064f0
+ | | 0x1a9e0c0
@@ -180410,0 +180423,9 @@
+ | |
+ | --0.00%-- 0x406520
+ | 0x4064f0
+ | |
+ | |--0.00%-- 0x1ad52a0
+ | |
+ | |--0.00%-- 0x1a0f2e0
+ | |
+ | --0.00%-- 0x1a9e0c0
$ wc -l callchain-result.{old,new}
191412 callchain-result.old
191433 callchain-result.new
382845 total
Thanks,
Namhyung
next prev parent reply other threads:[~2014-09-24 1:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 6:30 [PATCH 1/2] perf callchain: Create an address space per thread Namhyung Kim
2014-09-23 6:30 ` [PATCH 2/2] perf callchain: Use global caching provided by libunwind Namhyung Kim
2014-09-23 12:28 ` Jiri Olsa
2014-09-23 12:53 ` Namhyung Kim
2014-09-24 1:04 ` Namhyung Kim [this message]
2014-09-23 14:01 ` Arun Sharma
2014-09-24 2:24 ` Namhyung Kim
2014-09-24 13:45 ` Jean Pihet
2014-09-26 5:50 ` Namhyung Kim
2014-09-26 7:14 ` Jean Pihet
2014-09-29 2:35 ` Namhyung Kim
2014-09-23 12:24 ` [PATCH 1/2] perf callchain: Create an address space per thread Jiri Olsa
2014-09-23 12:49 ` Namhyung Kim
2014-09-26 15:35 ` Arnaldo Carvalho de Melo
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=878ul9ltg4.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=asharma@fb.com \
--cc=jean.pihet@linaro.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.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
Powered by JetHome