mirror of
https://github.com/DataDog/go-profiler-notes.git
synced 2026-06-23 09:56:47 +08:00
minor edits
This commit is contained in:
parent
6962c13040
commit
96b99cf724
3 changed files with 7 additions and 7 deletions
|
|
@ -6,8 +6,8 @@ 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 |
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue