mirror of
https://github.com/DataDog/go-profiler-notes.git
synced 2026-06-21 00:46:51 +08:00
Link stack traces
This commit is contained in:
parent
350a4ab46c
commit
8f7dcc4fc6
1 changed files with 1 additions and 0 deletions
|
|
@ -5,6 +5,7 @@ Hey there 👋🏻, I'm [felixge](https://github.com/felixge) and I've just star
|
|||
I found that Go has a lot of profilers and there are many tools for looking at the data, but that there is very little information on what any of it means. So in order to make sure that I know what I'm talking about, I've started to research the existing profilers and how they work. This repository is my attempt to summarize my findings in the hope that it might be useful to others.
|
||||
|
||||
- [pprof tool & format](./pprof.md): Describes the pprof tool and the binary data format for storing profiles.
|
||||
- [Stack Traces](./stack-traces.md): An in-depth look at stack traces in Go which are a load bearing subsystem for profiling.
|
||||
- [Goroutine Profiling](./goroutine.md): Allows you to get a list of all active goroutines and what they're currently doing.
|
||||
- [Block Profiling](./block.md): Understand how much time your code spends waiting on channels and locks.
|
||||
- CPU Profiling (🚧 coming soon!)
|
||||
|
|
|
|||
Loading…
Reference in a new issue