FAQ
Is there any way to tickle pprof into divulging caller information for
cnew and other runtime calls (runtime.convT2E, newdefer, etc.)? Or
better yet, just request that allocs from within runtime calls get
charged to their callers?

Thanks,
-josh

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Rémy Oudompheng at Sep 16, 2013 at 9:23 pm

    On 2013/9/16 Josh Bleecher Snyder wrote:
    Is there any way to tickle pprof into divulging caller information for
    cnew and other runtime calls (runtime.convT2E, newdefer, etc.)? Or
    better yet, just request that allocs from within runtime calls get
    charged to their callers?
    See https://code.google.com/p/go/source/detail?r=006117afcdfa

    I find the current behaviour (on tip) satisfying.

    Rémy.

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Josh Bleecher Snyder at Sep 16, 2013 at 10:58 pm

    Is there any way to tickle pprof into divulging caller information for
    cnew and other runtime calls (runtime.convT2E, newdefer, etc.)? Or
    better yet, just request that allocs from within runtime calls get
    charged to their callers?
    See https://code.google.com/p/go/source/detail?r=006117afcdfa

    I find the current behaviour (on tip) satisfying.
    Lovely. Thanks! Much improved.

    However, even with tip, I'm still seeing a non-trivial amount of
    runtime-y stuff. (It might be that what I'm profiling is not
    sufficiently interesting.) Thanks to that CL, in any case, I know
    where to muck around. :)

    What is the rule of thumb that guides whether or not a particular
    frame counts as uninteresting?

    -josh

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Sep 16, 2013 at 11:06 pm

    What is the rule of thumb that guides whether or not a particular
    frame counts as uninteresting?
    The caller, runtime methods don't call themselves. go tool pprof --pdf
    $BIN $PROF and have a look at the callers of the runtime methods.

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Josh Bleecher Snyder at Sep 17, 2013 at 1:09 am

    What is the rule of thumb that guides whether or not a particular
    frame counts as uninteresting?
    The caller, runtime methods don't call themselves. go tool pprof --pdf
    $BIN $PROF and have a look at the callers of the runtime methods.
    Thanks -- that's what I was looking for.

    The detour through the CL was very interesting, though! Thanks again, Rémy.

    -josh

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedSep 16, '13 at 8:51p
activeSep 17, '13 at 1:09a
posts5
users3
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase