mirror of
https://github.com/DataDog/go-profiler-notes.git
synced 2026-06-22 01:16:49 +08:00
disclaimers
This commit is contained in:
parent
900060c967
commit
7e70b778bf
5 changed files with 32 additions and 6 deletions
|
|
@ -28,3 +28,9 @@ I've just started a new job at [Datadog](https://www.datadoghq.com/) to work on
|
||||||
- [Profiling Go programs with pprof](https://jvns.ca/blog/2017/09/24/profiling-go-with-pprof/) by Julia Evans: A nice tour with a focus on heap profiling and the pprof output format.
|
- [Profiling Go programs with pprof](https://jvns.ca/blog/2017/09/24/profiling-go-with-pprof/) by Julia Evans: A nice tour with a focus on heap profiling and the pprof output format.
|
||||||
|
|
||||||
Got great links to recommend? Open an issue or PR, I'd happy to add your suggestions : ).
|
Got great links to recommend? Open an issue or PR, I'd happy to add your suggestions : ).
|
||||||
|
|
||||||
|
## Disclaimers
|
||||||
|
|
||||||
|
I work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go (you should check it out) and they generously allowed me to do all this research and publish it.
|
||||||
|
|
||||||
|
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
|
||||||
6
cpu.md
6
cpu.md
|
|
@ -76,6 +76,8 @@ The various ways one can record CPU profiles in Go are listed below.
|
||||||
- performance overhead
|
- performance overhead
|
||||||
- Discuss [Proposal: hardware performance counters for CPU profiling.](https://go.googlesource.com/proposal/+/refs/changes/08/219508/2/design/36821-perf-counter-pprof.md)
|
- Discuss [Proposal: hardware performance counters for CPU profiling.](https://go.googlesource.com/proposal/+/refs/changes/08/219508/2/design/36821-perf-counter-pprof.md)
|
||||||
|
|
||||||
## Disclaimer
|
## Disclaimers
|
||||||
|
|
||||||
I've just started a new job at [Datadog](https://www.datadoghq.com/) to work on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. This document may not reflect the views of my employer, but they were kind enough to let me publish it : ).
|
I work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out : ).
|
||||||
|
|
||||||
|
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
|
||||||
|
|
@ -28,4 +28,10 @@ The payload uses `multipart/form-data` encoding and includes the following form
|
||||||
- `types[0..n]`: The comma separates types included in each profile, e.g. `alloc_objects,alloc_space,inuse_objects,inuse_space`.
|
- `types[0..n]`: The comma separates types included in each profile, e.g. `alloc_objects,alloc_space,inuse_objects,inuse_space`.
|
||||||
- `data[0..n]`: One file field for each profile. The filename is always `pprof-data`, and the pprof data is compressed (by Go).
|
- `data[0..n]`: One file field for each profile. The filename is always `pprof-data`, and the pprof data is compressed (by Go).
|
||||||
|
|
||||||
TODO: Link to a sample payload file.
|
TODO: Link to a sample payload file.
|
||||||
|
|
||||||
|
## Disclaimers
|
||||||
|
|
||||||
|
I work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out : ).
|
||||||
|
|
||||||
|
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
|
||||||
10
goroutine.md
10
goroutine.md
|
|
@ -219,6 +219,12 @@ Below is a truncated example of the returned output, see [2.runtime.goroutinepro
|
||||||
|
|
||||||
This package exposes the [`pprof.Lookup("goroutine")`](https://golang.org/pkg/runtime/pprof/#Lookup) profiles described above via HTTP endpoints. The output is identical.
|
This package exposes the [`pprof.Lookup("goroutine")`](https://golang.org/pkg/runtime/pprof/#Lookup) profiles described above via HTTP endpoints. The output is identical.
|
||||||
|
|
||||||
## Disclaimer
|
## History
|
||||||
|
|
||||||
I've just started a new job at [Datadog](https://www.datadoghq.com/) to work on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. This document may not reflect the views of my employer, but they were kind enough to let me publish it : ).
|
Goroutine profiling was [implemented](https://codereview.appspot.com/5687076/) by [Russ Cox](https://github.com/rsc) and first appeared in the [weekly.2012-02-22](https://golang.org/doc/devel/weekly.html#2012-02-22) release prior to go1.
|
||||||
|
|
||||||
|
## Disclaimers
|
||||||
|
|
||||||
|
I work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out : ).
|
||||||
|
|
||||||
|
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
|
||||||
8
heap.md
8
heap.md
|
|
@ -37,4 +37,10 @@ GODEBUG=gctrace=1 go run <code>
|
||||||
|
|
||||||
- The [docs](https://golang.org/pkg/runtime/pprof/#Profile) say I should get some kind of data, even if there is no GC. I can reproduce that, but the data seems to not change?
|
- The [docs](https://golang.org/pkg/runtime/pprof/#Profile) say I should get some kind of data, even if there is no GC. I can reproduce that, but the data seems to not change?
|
||||||
|
|
||||||
> If there has been no garbage collection at all, the heap profile reports all known allocations. This exception helps mainly in programs running without garbage collection enabled, usually for debugging purposes.
|
> If there has been no garbage collection at all, the heap profile reports all known allocations. This exception helps mainly in programs running without garbage collection enabled, usually for debugging purposes.
|
||||||
|
|
||||||
|
## Disclaimers
|
||||||
|
|
||||||
|
I work at [Datadog](https://www.datadoghq.com/) on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. You should check it out : ).
|
||||||
|
|
||||||
|
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!
|
||||||
Loading…
Reference in a new issue