go/go-profiler-notes
1
0
Fork 0
mirror of https://github.com/DataDog/go-profiler-notes.git synced 2025-07-12 23:50:13 +02:00
Code Issues Releases 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
Download Patch File Download Diff File Expand all files Collapse all files

2
block.md
View File

@ -271,4 +271,4 @@ Block profiling was [implemented](https://codereview.appspot.com/6443115) by [Dm
I'm [felixge](https://github.com/felixge) and work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out. We're also [hiring](https://www.datadoghq.com/jobs-engineering/#all&all_locations) : ).
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!

2
goroutine.md
View File

@ -241,4 +241,4 @@ Goroutine profiling was [implemented](https://codereview.appspot.com/5687076/) b
I'm [felixge](https://github.com/felixge) and work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out. We're also [hiring](https://www.datadoghq.com/jobs-engineering/#all&all_locations) : ).
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!

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:
| stack trace | samples/count |
| ------------ | ------------- |
| main;foo | 5 |
| main;foo;bar | 3 |
| main;foobar | 4 |
| stack trace | count |
| ------------ | ----- |
| main;foo | 5 |
| main;foo;bar | 3 |
| 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: