1
0
mirror of https://github.com/DataDog/go-profiler-notes.git synced 2025-07-12 23:50:13 +02:00

fix broken links

This commit is contained in:
Felix Geisendörfer
2022-10-14 08:20:59 +02:00
parent bb9b9ec34f
commit 83eeb79a9a

View File

@ -1,6 +1,6 @@
# block-net
This [program](./main.go) explores the [question](https://twitter.com/rogpeppe/status/1359202847708037124) whether network i/o (e.g. waiting on socket read/write operations) will show up in the [block profiler](/block.md) or not.
This [program](./main.go) explores the [question](https://twitter.com/rogpeppe/status/1359202847708037124) whether network i/o (e.g. waiting on socket read/write operations) will show up in the [block profiler](../../block.md) or not.
The program does the following:
@ -22,5 +22,5 @@ However, as you can see below, the block profiler [captures](./block.pb.gz) only
![block-net](./block-net.png)
This means that [block profiler](/block.md) is generally not able to give a good idea about goroutines that are waiting on network i/o.
This means that [block profiler](../../block.md) is generally not able to give a good idea about goroutines that are waiting on network i/o.