From a5c718c08ea22c8906f837c1265c3755daca8b58 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Fri, 19 Feb 2021 15:36:31 +0100 Subject: [PATCH] Better link descriptions --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 923da4e..33e7796 100644 --- a/README.md +++ b/README.md @@ -4,9 +4,9 @@ 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 it's binary data format. -- [Goroutine Profiling](./goroutine.md) -- [Block Profiling](./block.md) +- [pprof tool & format](./pprof.md): Describes the pprof tool and the binary data format for storing profiles. +- [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 networking, locks and channel operations. - CPU Profiling (🚧 coming soon!) - Heap Profiling (🚧 coming soon!) - Mutex Profiling (🚧 coming soon!)