 |
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=006117afcdfaI 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.
