Em Wed, Nov 26, 2014 at 01:47:41PM +0100, Milian Wolff escreveu:
> I wonder whether there is a way to reduce the size of perf data files. Esp.
> when I collect call graph information via Dwarf on user space applications, I
> easily end up with multiple gigabytes of data in just a few seconds.
> I assume currently, perf is built for lowest possible overhead in mind. But
> could maybe a post-processor be added, which can be run after perf is
> finished
> collecting data, that aggregates common backtraces etc.? Essentially what I'd
> like to see would be something similar to:
> perf report --stdout | gzip > perf.report.gz
> perf report -g graph --no-children -i perf.report.gz
> Does anything like that exist yet? Or is it planned?
No, it doesn't, and yes, it would be something nice to have, i.e. one
that would process the file, find the common backtraces, and for that
probably we would end up using the existing 'report' logic and then
refer to those common backtraces by some index into a new perf.data file
section, perhaps we could use the features code for that...
But one thing you can do now to reduce the size of perf.data files with
dwarf callchains is to reduce the userspace chunk it takes, what is
exactly the 'perf record' command line you use?
The default is to get 8KB of userspace stack per sample, from
'perf record --help':
-g enables call-graph recording
--call-graph <mode[,dump_size]>
setup and enables call-graph (stack chain/backtrace)
recording: fp dwarf
-v, --verbose be more verbose (show counter open errors, etc)
So, please try with something like:
perf record --call-graph dwarf,512
And see if it is enough for your workload and what kind of effect you
notice on the perf.data file size. Play with that dump_size, perhaps 4KB
would be needed if you have deep callchains, perhaps even less would do.
Something you can use to speed up the _report_ part is:
--max-stack <n> Set the maximum stack depth when parsing the
callchain, anything beyond the specified depth
will be ignored. Default: 127
But this won't reduce the perf.data file, obviously.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
