XeLabs/go-profiler-notes
2
0
Fork 0
mirror of https://github.com/DataDog/go-profiler-notes.git synced 2026-06-22 09:26:53 +08:00
Code Issues Projects Releases Wiki Activity

minor edits

Browse source
This commit is contained in:
Felix Geisendörfer 2021-03-18 11:03:11 +01:00
parent 6962c13040
commit 96b99cf724
3 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
stack-traces.md
View file

@ -6,11 +6,11 @@ Stack traces play a critical role in Go profiling. So let's try to understand th
All Go profilers work by collecting samples of stack trace and putting them into [pprof profiles](./pprof.md). Ignoring some details, a pprof profile is just a frequency table of stack traces like shown below: All Go profilers work by collecting samples of stack trace and putting them into [pprof profiles](./pprof.md). Ignoring some details, a pprof profile is just a frequency table of stack traces like shown below:
| stack trace | samples/count | | stack trace | count |
| ------------ | ------------- | | ------------ | ----- |
| main;foo | 5 | | main;foo | 5 |
| main;foo;bar | 3 | | main;foo;bar | 3 |
| main;foobar | 4 | | main;foobar | 4 |
Let's zoom in on the second stack trace in the table above: `main;foo;bar`. A Go developer will usually be more familiar with seeing a stack trace like this as rendered by `panic()` or [`runtime.Stack()`](https://golang.org/pkg/runtime/#Stack) shown below: Let's zoom in on the second stack trace in the table above: `main;foo;bar`. A Go developer will usually be more familiar with seeing a stack trace like this as rendered by `panic()` or [`runtime.Stack()`](https://golang.org/pkg/runtime/#Stack) shown below: