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

fix typo

Browse source
This commit is contained in:
Felix Geisendörfer 2022-02-10 02:16:56 +01:00 committed by GitHub
parent a29db3c1ce
commit b8feda3caa
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
guide/README.md
View file

@ -1,4 +1,4 @@
⬅ [Index of all go-profiler-notes](../README.md)
li⬅ [Index of all go-profiler-notes](../README.md)
# The Busy Developer's Guide to Go Profiling, Tracing and Observability
- **[Introduction](#introduction):** [Read This](#read-this) · [Mental Model for Go](#mental-model-for-go) · Profiling vs Tracing
@ -339,7 +339,7 @@ The `free_*` counters themselves are not included in the final memory profile. I
There are a few known issues and limitations of the memory profiler that you might want to be aware of:
- 🐞 [GH #49171](https://github.com/golang/go/issues/49171): Delta profiles (taken with e.g. `GET /debug/pprof/allocs?seconds=60`) may report negative allocation counts due to symbolization bug for inlined closures in Go 1.17. It's fixed in Go 1.18.
- 🐞 [GH #49171](https://github.com/golang/go/issues/49171): Delta profiles (taken with e.g. `GET /debug/pprof/allocs?seconds=60`) may report negative allocation counts due to a symbolization bug involving inlined closures in Go 1.17. It's fixed in Go 1.18.
- ⚠️ [`runtime.MemProfileRate`](https://pkg.go.dev/runtime#MemProfileRate) must only be modified once, as early as possible in the startup of the program; for example, at the beginning of `main()`. Writing this value is inherently a small data race, and changing it multiple times during program execution will produce incorrect profiles.
- ⚠ When debugging potential memory leaks, the memory profiler can show you where those allocations were created, but it can't show you which references are keeping them alive. A few attempts to solve this problem were made over the years, but none of them work with recent versions of Go. If you know about a working tool, please [let me know](https://github.com/DataDog/go-profiler-notes/issues).
- ⚠ [CPU Profiler Labels](#cpu-profiler-labels) or similar are not supported by the memory profiler. It's difficult to add this feature to the current implementation as it could create a memory leak in the internal hash map that holds the memory profiling data.