Yes, that’s what I was referring to. It is much easier then the graph in some cases.
Also github.com/robaho/goanalyzer might help depending on the workload >> On Oct 21, 2019, at 2:10 AM, Than McIntosh <th...@google.com> wrote: > > It can sometimes be useful in such situations to look at the pprof "tree" > output style (as opposed to graph). > > Than > > >>> On Sat, Oct 19, 2019 at 4:14 AM Piers Powlesland >>> <pierspowlesl...@gmail.com> wrote: >> Kind of, but due to the sheer number of nodes and edged the edges end up >> lying on top of each other so in certain cases you end up having to check >> the source of several nodes to see which is the caller. >> >>>> On Sat, 19 Oct 2019, 03:08 Robert Engels, <reng...@ix.netcom.com> wrote: >>> But also can’t you just find that node in the graph and see the callers? >>> >>>>> On Oct 18, 2019, at 8:54 PM, Robert Engels <reng...@ix.netcom.com> wrote: >>>> >>>> Yes. When using the command pprof viewer there is a way to show the >>>> hotspots with the callers. Again I don’t have access to dev at the moment. >>>> >>>>>> On Oct 18, 2019, at 8:44 PM, Piers Powlesland >>>>>> <pierspowlesl...@gmail.com> wrote: >>>>> >>>>> Hi Robert, >>>>> >>>>> I think I found the options you were referring to, and I was able to get >>>>> the whole overview with the following. >>>>> >>>>> go tool pprof -http :9999 -edgefraction 0 -nodefraction 0 -nodecount >>>>> 100000 cpu.prof >>>>> >>>>> Its a bit of a screenfull though, and I was wondering if there is any >>>>> simpler way to find out who is calling what? >>>>> So that I could dig down through top and if the function isn't in my code >>>>> follow the callstack to find what part of my code >>>>> initiated the call. >>>>> >>>>>>> On Fri, Oct 18, 2019 at 8:52 PM Robert Engels <reng...@ix.netcom.com> >>>>>>> wrote: >>>>>> I am pretty sure there is a way to filter nodes that are less than X %, >>>>>> and some of that filtering is on by default - so you may want to turn >>>>>> that off (can't say for sure since not at dev machine right now). >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> >From: Ian Lance Taylor <i...@golang.org> >>>>>> >Sent: Oct 18, 2019 2:43 PM >>>>>> >To: Piers Powlesland <pierspowlesl...@gmail.com> >>>>>> >Cc: golang-nuts <golang-nuts@googlegroups.com> >>>>>> >Subject: Re: [go-nuts] pprof not showing call hierarchy for time.now >>>>>> >and time.Until >>>>>> > >>>>>> >On Fri, Oct 18, 2019 at 12:37 PM <pierspowlesl...@gmail.com> wrote: >>>>>> >> >>>>>> >> I used pprof to get an overview of where time is being spent in my >>>>>> >> latest project and I'm >>>>>> >> getting a result I don't understand. When using the web view, there >>>>>> >> are certain function >>>>>> >> calls that are taking up a large percentage of the time but they >>>>>> >> appear un-rooted as in >>>>>> >> there seems to be no parent call calling them. >>>>>> >> >>>>>> >> I have attached a picture of the web view showing just the un-rooted >>>>>> >> functions. >>>>>> >> >>>>>> >> I generated the profile with the following command. >>>>>> >> >>>>>> >> go test -cpuprofile cpu.prof -count 4 . -run MyTest >>>>>> >> >>>>>> >> and I viewed the profile with the following command. >>>>>> >> >>>>>> >> go tool pprof -http :9999 cpu.prof >>>>>> >> >>>>>> >> I'd really like to track down what is causing all this time in the >>>>>> >> time package, but I'm >>>>>> >> at a bit of a loss. >>>>>> > >>>>>> >Which version of Go and which GOOS/GOARCH? There have been bugs in >>>>>> >this area in the past, and at least some of them are fixed in 1.13. >>>>>> > >>>>>> >Ian >>>>>> > >>>>>> >-- >>>>>> >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/CAOyqgcWReW9e79szp29F11nmvVEzhZr7O%3D1Qp5WXkGBLwWprBA%40mail.gmail.com. >>>> -- >>>> 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/876AA5BF-E048-4A7D-8842-9E40B3F9FA26%40ix.netcom.com. >> >> -- >> 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/CAFXacX%3DJrvC8VqUs%2BCQr0SOBgfH4vtO5fyrYGVFidduH067OrA%40mail.gmail.com. -- 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/E31A604E-A221-407F-8EEB-54E74E7454E8%40ix.netcom.com.
