All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: -fno-omit-frame-pointer
Date: Sat, 21 Feb 2015 14:09:50 -0800	[thread overview]
Message-ID: <mcavng$p5n$1@ger.gmane.org> (raw)
In-Reply-To: alpine.DEB.2.00.1502211252520.27009@cobra.newdream.net

Sage Weil wrote:

> Hey Mark,
> 
> I just watched Brendan Gregg's talk at SCALE (which was extremely good)
> and one of the things he mentioned is the importance of
> -fno-omit-frame-pointer.  I notice we are setting it via do_autogen.sh
> (i.e., for developers) but not in the production builds.  Should we be?
> I think it's important to be able to get meaningful callgraph output from
> production deployments and I suspect there is minimal performance impact.
> 
> http://www.slideshare.net/brendangregg/scale2015-linux-perfprofiling

I personally favor DWARF-based unwinding - for one, on register-starved 
architectures such as 32-bit x86, the frame pointer itself can skew 
performance.

With regard to it inflating instance size, that's something that can be 
mitigated - via split debuginfo (only pull in the ones you actually need), 
compressed debug info (zlib -9 shrinks it a good bit), and semantic 
deduplication/compression with dwz.


  reply	other threads:[~2015-02-21 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21 21:43 -fno-omit-frame-pointer Sage Weil
2015-02-21 22:09 ` Alex Elsayed [this message]
2015-02-21 23:27 ` -fno-omit-frame-pointer Mark Nelson
2015-02-23 18:28   ` -fno-omit-frame-pointer Sage Weil
2015-02-23 18:30     ` -fno-omit-frame-pointer Sage Weil
2015-02-23 21:35   ` -fno-omit-frame-pointer Mark Nelson

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='mcavng$p5n$1@ger.gmane.org' \
    --to=eternaleye@gmail.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.