Hi,
I just ran coz on a project of mine a few days ago.
Building it properly was a little bit of trail and error to figure how out
how get the build to play nice with the profiler but eventually I got it
working.
For builds, use
go build -o -ldflags=-compressdwarf=false
So that coz can read the debug symbols properly.
I made a small wrapper repo here: https://github.com/urjitbhatia/cozgo
In terms of actual profiler output, I got some useful info but it isn't
something that regular profiling tools didn't tell me so far. (That I
memory allocation is kinda slow for me right now).
[image: Screen Shot 2019-10-02 at 4.21.09 PM.png]
I think I need to run a longer, slightly more varied loadtest on the
application to exercise more of the profiler.
On Tuesday, October 1, 2019 at 8:13:08 PM UTC-7, Gerald Stan wrote:
>
> Hi, interesting work. @Ingo is that the only way run casual profiling in
> go?
>
--
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/e69eca97-0597-492a-ab36-6dc9b762b9e1%40googlegroups.com.
