go/go-profiler-notes
1
0
Fork 0
mirror of https://github.com/DataDog/go-profiler-notes.git synced 2025-07-15 23:54:16 +02:00
Code Issues Releases Activity

fix broken links (#20)

Browse Source 
* fix broken links

* remove non-existing link
This commit is contained in:
Felix Geisendörfer
2022-10-14 08:23:41 +02:00
committed by GitHub
parent bb9b9ec34f
commit 63feabe270
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
block.md
View File

@ -166,7 +166,7 @@ Below is an example of block profile encoded in [pprof's protobuf format](./ppro
- contentions/count
- delay/nanoseconds
The `blockprofilerate` used to create the profile is not included, neither are [profiler labels](./profiler-labels).
The `blockprofilerate` used to create the profile is not included, neither are profiler labels.
```
$ go tool pprof -raw block.pb.gz

4
examples/block-net/README.md
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.