You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Go 1.8, if I wanted to see where in the runtime allocations came from, I could use memory profiling and then run go tool pprof with the -runtime flag. The -runtime flag is absent on tip, and it appears (from trying out the 1.8 pprof tool on the tip profiles) that the data is not being recorded either. This is an impediment to optimizing the runtime.
Perhaps unrelatedly, the 1.8 pprof tool usefully lists the heap profile display modes in its help text:
Pprof has moved responsibility for this filtering into the profile generators, which is where it belongs. (Pprof shouldn't have a list of magic Go runtime symbols in its source code.) Unfortunately, this means we can't support the -runtime flag.
For your own debugging you can change src/runtime/pprof/protomem.go to say hideRuntime := false. I'm not sure whether we should introduce new API to make that possible to trigger without patching.
In Go 1.8, if I wanted to see where in the runtime allocations came from, I could use memory profiling and then run go tool pprof with the -runtime flag. The -runtime flag is absent on tip, and it appears (from trying out the 1.8 pprof tool on the tip profiles) that the data is not being recorded either. This is an impediment to optimizing the runtime.
Perhaps unrelatedly, the 1.8 pprof tool usefully lists the heap profile display modes in its help text:
The tip pprof tool does not.
cc @rsc @matloob
The text was updated successfully, but these errors were encountered: