From bd6440d86192e714b285f71001d4e090f36676d0 Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Mon, 6 Aug 2018 13:52:44 +0200 Subject: update --- _posts/2017-03-07-golang-profiling-simplified.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to '_posts/2017-03-07-golang-profiling-simplified.md') diff --git a/_posts/2017-03-07-golang-profiling-simplified.md b/_posts/2017-03-07-golang-profiling-simplified.md index f74c7b2..5b9f6ed 100644 --- a/_posts/2017-03-07-golang-profiling-simplified.md +++ b/_posts/2017-03-07-golang-profiling-simplified.md @@ -4,6 +4,15 @@ title: Golang profiling simplified description: Golang profiling made easy --- +**Table of content** + +- [Where are my pprof files?](#where-are-my-pprof-files) +- [Why is my cpu profile empty?](#why-is-my-cpu-profile-empty) +- [Profiling](#profiling) + - [Memory profiling](#memory-profiling) + - [CPU profiling](#cpu-profiling) + - [Generating profiling reports](#generating-profiling-reports) + Many posts have been written regarding profiling in Golang and I haven’t found proper tutorial regarding this. Almost all of them are missing some part of important information and it gets pretty frustrating when you have a deadline and are not finding simple distilled solution. Nevertheless, after searching and experimenting I have found a solution that works for me and probably should also for you. -- cgit v1.2.3