The documentation is not clear regarding what exactly pprof shows. Here are a few examples.

go tool pprof -http=":8081" http://localhost:8080/debug/pprof/profile?seconds=30

Let's open the flamegraph. There are at least two possibilities:

1. The flamegraph shows the clock time spent with given stacktrace
2. The flamegraph shows on-CPU time spent with given stacktrace, i.e. clock time excluding the time spent waiting for disk/network I/O or execution of other programs.

Since I/O can be quite slow these are very different options. Both reports are useful depending on what bottleneck we are trying to fix (I/O or CPU).

go tool pprof -http=":8081" http://localhost:8080/debug/pprof/heap

I'm assuming the flamegraph shows places where given amount of memory was allocated. However it's not clear whether this is 1) the total amount of allocated memory (i.e. it doesn't matter if it was freed), 2) amount of allocated memory of objects that are currently alive, or 3) amount of memory of objects that are not garbage collected yet. Without proper documentation there is no way to tell which option, if any, is correct.

go tool pprof -http=":8081" http://localhost:8080/debug/pprof/block

The time shown doesn't make much sense. On the flamegraph I see something like 18988816179 usec i.e. 5 hours. However the program was executing only for a few minutes. I guess the time should be divided by the number of CPUs or maybe by the number of goroutines (what if it varies?).