From 9dd768079fb41627e322217565f74b22095f8395 Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Tue, 25 Sep 2018 12:47:34 +0200 Subject: content update --- _posts/2017-03-07-golang-profiling-simplified.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (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 c6cf78e..2b5a262 100644 --- a/_posts/2017-03-07-golang-profiling-simplified.md +++ b/_posts/2017-03-07-golang-profiling-simplified.md @@ -6,12 +6,12 @@ description: Golang profiling made easy **Table of contents** -- [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) +1. [Where are my pprof files?](#where-are-my-pprof-files) +2. [Why is my cpu profile empty?](#why-is-my-cpu-profile-empty) +3. [Profiling](#profiling) + 1. [Memory profiling](#memory-profiling) + 2. [CPU profiling](#cpu-profiling) + 3. [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. -- cgit v1.2.3