From 8f7dcc4fc64e58bfb8e6f93cee27bf238e4bc275 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Mon, 24 May 2021 12:47:50 +0200 Subject: [PATCH] Link stack traces --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 546baae..56cf912 100644 --- a/README.md +++ b/README.md @@ -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!)