I'd love to hear from folks about your experiences. Do you use execution tracing often. If not, is it due to lack of need, lack of documentation, missing information, tooling issues, etc?

Go's execution tracer is a woefully underutilized tool. It contains tons of information about what is happening at any given moment that you won't get with a profile. In addition to showing flight recording capabilities, this post provides a nice example of how to use tracing to diagnose a problem.

“Flight Recorder in Go 1.25” by Carlos Amedee and Michael Knyszek — https://go.dev/blog/flight-recorder #golang

The GopherCon EU videos are online. I really enjoyed @misago.org’s about testing/synctest. But there were so many good talks, maybe watch them all? youtu.be/oIC3zhTAOsY #gopherconeu #golang

My GopherCon EU talk about Swiss Table maps is now available! youtu.be/aqtIM5AK9t4

What if Go’s garbage collector could just run faster? Join @michael.express from the Go Team for a deep dive into Green Tea — a new experimental parallel mark algorithm designed to speed up Go’s garbage collector through better cache locality and SIMD. www.gophercon.com/agenda/sessi...

Thanks @commaok.xyz for hosting @michael.express and I to talk about a fun bug in Go’s new Green Tea GC and the tools we used to investigate. sigpod.dev/6

New experimental garbage collector for Go programs! github.com/golang/go/is...

How often do people run into the SetFinalizer footguns in Go? (Accidental cycle, for example.) Would a GODEBUG that does something slow but tells you when you've made a mistake be useful to you? (Maybe even just for tests, to prevent a regression?) Sketch: go-review.googlesource.com/c/go/+/634599