[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Nov 2013 07:44:37 -0700
From: David Ahern <dsahern@...il.com>
To: Ingo Molnar <mingo@...nel.org>
CC: Namhyung Kim <namhyung@...nel.org>,
Pekka Enberg <penberg@...nel.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Stephane Eranian <eranian@...gle.com>,
Jiri Olsa <jolsa@...hat.com>,
Rodrigo Campos <rodrigo@...g.com.ar>,
Arun Sharma <asharma@...com>
Subject: Re: [RFC/PATCHSET 00/14] perf report: Add support to accumulate hist
periods (v2)
On 11/11/13, 5:19 AM, Ingo Molnar wrote:
>
> In what way is call-graph profiling utilized typically?
>
> Is it system-wide, i.e. something like:
>
> perf record -a -g sleep 10
>
> ? If yes then that would explain why scalability problems rarely surfaced,
> it takes a longer user-space profile to get to the event counts where
> scalability started hurting.
Both. But not time periods long enough to generate GB sized files
(limitations in the product). I get various reports of hung commands
(usually perf-not terminated properly (now fixed) or the file is
corrupted on transfer), but noone has complained to me about perf-report
appearing to hang or for 20-30 minutes to generate a result.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists