From: Mark Nelson <mark.nelson@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Profiling with Perf
Date: Wed, 12 Nov 2014 14:42:35 -0600 [thread overview]
Message-ID: <5463C63B.2070502@redhat.com> (raw)
In-Reply-To: <5462C456.8070601@redhat.com>
Hi, there was a question on the performance call today about how to use
dwarf symbols in perf. Roughly:
1) Make sure during the kernel/perf compile that libunwind is used.
This can be tricky depending on how you build the kernel, but
theoretically should work.
2) invoke perf using something like:
"perf record -g dwarf -F 100 -a"
This tells perf to use dwarf symbols but limit the sampling rate. perf
can generate a *lot* of data with dwarf symbols and default sampling.
3) Look at results in perf report as normal.
4) Profit!
Theoretically if you have frame pointers enabled when you compile ceph
you should get good symbol resolution without dwarf but I've never
gotten it to work well. Perf+Dwarf seems to give much better symbol
resolution than anything else I've tried with Ceph. There's some new
LBR functionality for profiling on Haswell in perf that might work too,
but I haven't tried it:
https://lkml.org/lkml/2014/10/19/166
Mark
next prev parent reply other threads:[~2014-11-12 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 2:22 Reminder: 11/12/2014 Weekly Ceph Performance Meeting Mark Nelson
2014-11-12 20:42 ` Mark Nelson [this message]
2014-11-12 20:59 ` Profiling with Perf Milosz Tanski
2014-11-12 21:16 ` Mark Nelson
2014-11-13 7:04 ` Alexandre DERUMIER
2014-11-14 21:38 ` Milosz Tanski
2014-11-14 21:33 ` Milosz Tanski
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=5463C63B.2070502@redhat.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.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 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.