public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [RFC/PATCH] perf record: Save build-id of DSO in callchains
Date: Tue, 24 Mar 2015 08:30:26 +0900	[thread overview]
Message-ID: <20150323233026.GF2782@sejong> (raw)
In-Reply-To: <551018C5.4030304@gmail.com>

Hi David,

On Mon, Mar 23, 2015 at 07:44:37AM -0600, David Ahern wrote:
> On 3/23/15 2:18 AM, Namhyung Kim wrote:
> >>Just curious, could you try to measure the performance impact of this
> >>change?
> >
> >   $ time perf record --call-graph dwarf -o kbuild.xxx -a -- sleep 30
> >   [ perf record: Woken up 34674 times to write data ]
> >   [ perf record: Captured and wrote 9538.729 MB kbuild.xxx (1211997 samples) ]
> >
> >   real   0m32.244s
> >   user   0m1.097s
> >   sys    0m8.997s
> >
> >   $ time perf record --call-graph dwarf -o kbuild.yyy --buildid-callchain -a -- sleep 30
> >   [ perf record: Woken up 40902 times to write data ]
> >   [ perf record: Captured and wrote 11208.500 MB kbuild.yyy (1433922 samples) ]
> >
> >   real   2m21.695s
> >   user   1m33.127s
> >   sys    0m22.077s
> >
> 
> How many CPUs and processes?

I was running kbuild with allyesconfig on 12-cpu box.

Thanks,
Namhyung

      parent reply	other threads:[~2015-03-23 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  1:18 [RFC/PATCH] perf record: Save build-id of DSO in callchains Namhyung Kim
2015-03-23  7:22 ` Ingo Molnar
2015-03-23  8:18   ` Namhyung Kim
2015-03-23 13:44     ` David Ahern
2015-03-23 16:28       ` Arnaldo Carvalho de Melo
2015-03-23 23:30       ` Namhyung Kim [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=20150323233026.GF2782@sejong \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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