Excellent stuff. I remember finding out about trace over here https://groups.google.com/forum/#!topic/golang-nuts/Ktvua7AGdkI
and I marvelled that there wasn't any documentation, so it was all trial and error for me. But what a gem. What a gem. Both the tool and your blog post. On Thursday, 6 April 2017 18:29:22 UTC+2, Will Sewell wrote: > > Hi, I've just written a blog post/tutorial on Go's relatively unknown, but > incredibly useful, trace visualiser: `go tool trace`. The post provides a > tour of the interface, and examples of the kind of problems it can aid in > tracking down. > > I was originally made aware of it by Rhys Hiltner in my previous message > to this mailing list when I was investigating long GC pause times: > https://groups.google.com/d/msg/golang-nuts/nOD0fGmRp_g/4FEThB1bBQAJ. So > thanks for pointing it out Rhys! As he mentions in that thread, it is > currently not well documented, so I felt it was a good opportunity for a > blog post after playing around with it for a bit. > > In the future I'd like to investigate and write about how the runtime > event system itself actually works because it seems like an interesting > area. > > Let me know if you have any feedback. > > Thanks, > Will > -- 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. For more options, visit https://groups.google.com/d/optout.
