Your Go application does not perform as well as you hoped in production. You connect to it, get an execution trace, open it – and it looks like a cardiogram of 22 football players. So, how do you make sense of it? Unfortunately, you have almost no chance if that’s the first time you see it.

It takes some time to get the experience and develop the intuition about backend performance in general and Go applications in particular. That intuition would help you to recognize specific patterns in those cardiograms like a doctor. My talk would allow you to start on this journey, starting with simple teaching examples and ending with real performance problems of production software.