[go-nuts] Re: question about Profiling Go Programs sample.

Vladimir, one more question. Does it mean that it is impossible to display recursive call in web by use pprof, it is necessary to use some additional tool, right ? четверг, 30 сентября 2021 г. в 11:38:49 UTC+3, alex-coder: > a little bit more resources: > golang pprof 实战 | Wolfogre's Blog >

[go-nuts] Re: question about Profiling Go Programs sample.

a little bit more resources: golang pprof 实战 | Wolfogre's Blog it seems to be in Chinese (I may be wrong), but thanks to google. четверг, 30 сентября 2021 г. в 09:55:17 UTC+3, alex-coder: > Hi > >>I think this is expected > you are experienced.

[go-nuts] Re: question about Profiling Go Programs sample.

Hi >>I think this is expected you are experienced. >> Depending on what you're looking for, firstly, I want to learn how to use pprof properly and secondly, I even could not imagine that it is not my mistake or not using tool properly.. thank you so much.:-) среда, 29 сентября 2021 г. в 21:55:

[go-nuts] Re: question about Profiling Go Programs sample.

Hey there, > I took runtime/cpuprof.go with version 1.4, where cpuprof.go just appeared with the same result. :-) I think this is expected. Go 1.4 was released in 2014 — several years after the original post about pprof, had been published. In fact, Go 1.4 is the version where the relevant p

[go-nuts] Re: question about Profiling Go Programs sample.

Vladimir, I took runtime / cpuprof.go with version 1.4, where cpuprof.go just

[go-nuts] Re: question about Profiling Go Programs sample.

Ok, thank you. Vladimir, is there any resource to read about current and probably future of the go profiling ? In fact it is not only very important but and very, very interesting. Thank you. вторник, 28 сентября 2021 г. в 06:38:31 UTC+3, vlad...@varank.in: > Hello, > > I suspect this is due

[go-nuts] Re: question about Profiling Go Programs sample.

Hello, I suspect this is due to how the current version of Go runtime's CPU profiler keeps only up to 64 items, when it builds the function's stack frame (refer to https://github.com/golang/go/blob/go1.17/src/runtime/cpuprof.go#L21) With that, the resulting profile misses the relationship betw