That's a great blog post, Will. Thanks for that. The Go team should have provided one for you, I must say, so double thanks.
-rob On Thu, Apr 6, 2017 at 10:00 AM, Will Sewell <m...@willsewell.com> wrote: > Apologies. I just realised I didn't actually link to the post! It's here: > https://making.pusher.com/go-tool-trace/. > > > On Thursday, 6 April 2017 17:29:22 UTC+1, 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. > -- 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.
