causal profiling in Go

[Ingo Oeser]

Hi everyone,

does someone has experience with causal profiling in Go? (see http://www.sigops.org/sosp/sosp15/current/2015-Monterey/printable/090-curtsinger.pdf if you are not aware of that topic)

Please note that I am aware of https://morsmachine.dk/causalprof but I want to hear a few more opinions on this.

I am also aware of the standard go profiling.

So anyone else who tried Daniels work?

Best Regards

Ingo

[Vincent Blanchon]

That's interesting, thanks for sharing.

Also interested to know if someone got results with a similar approach.

[Gerald Stan]

Hi, interesting work. @Ingo is that the only way run casual profiling in go?

[Urjit Singh Bhatia]

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 <yourbinary> -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).

I think I need to run a longer, slightly more varied loadtest on the application to exercise more of the profiler.