I’m trying to compare the efficiency of two binaries before and after 
applying Profile-Guided Optimization . For this, I’m using Go’s profiling, 
specifically the flame graph. However, I’m getting two almost identical 
stacks; the only difference is that some functions are inlined. It seems 
that pprof doesn’t recognize that these functions are part of the same 
execution path. I need to understand the percentage of improvement I’m 
getting when compiling with PGO.

My question is: Is there a way to indicate to pprof that these two paths 
are part of the same execution? Or, is there a way to measure the 
improvement obtained with PGO?"

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/11628d55-73c3-44e1-91bf-8fcc8adb1631n%40googlegroups.com.

Reply via email to