From: Andi Kleen <andi@firstfloor.org>
To: Yale Zhang <yzhang1985@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Size of perf data files
Date: Mon, 05 Jan 2015 21:39:49 -0800 [thread overview]
Message-ID: <87ppas31sq.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CALQF7ZygJpx=Lf0Dc70=cRRCheF_8SFos8sv8z0kjiog2Do0Zg@mail.gmail.com> (Yale Zhang's message of "Mon, 5 Jan 2015 19:21:22 -0800")
Yale Zhang <yzhang1985@gmail.com> writes:
> Perf developers,
> I'm also very interested in reducing the size of the data files when
> reporting call stacks. Currently, profiling 30s of execution with call
The simplest way is to lower the frequency. Especially don't
use adaptive frequency (which is the default). This also
lowers overhead quite a bit. Also don't use dwarf unwinding.
It is very expensive.
There are some other ways.
I suspect you would most of what you want by just running
a fast compressor (snappy or LZO) at perf record time. That would
be likely a useful addition.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-01-06 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 3:21 Size of perf data files Yale Zhang
2015-01-06 5:39 ` Andi Kleen [this message]
2015-01-06 21:02 ` Yale Zhang
2015-01-06 21:29 ` Andi Kleen
2015-01-09 2:06 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2014-11-26 12:47 Milian Wolff
2014-11-26 16:06 ` Arnaldo Carvalho de Melo
2014-11-26 18:11 ` Milian Wolff
2014-11-27 0:56 ` Namhyung Kim
2014-11-27 13:19 ` Arnaldo Carvalho de Melo
2014-11-28 6:18 ` Namhyung Kim
2014-11-26 20:48 ` Andi Kleen
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=87ppas31sq.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=yzhang1985@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.