September 26th, 2017
Meetup related material
pprof -> no clue about how many CPU we used. trace -> understand the process time and channel send -> channel recev
“Synchronization blocking profile” is a good clue to figure out problem related to unbuffered channel.
Execution-tracer also help to figure out problem when you trace running http server. It could help us to figure out network request and http serve diagram.
View Option -> Flow Arrow to display all the incoming and outcoming flow.
Goroutine announce -> to understand the goroutine path
Execution tracker is low overhead, until the lots golang routine waiting (not must but almost 10%).