From 5845a5be3c0cc86d6fca3c44e26f9cbf77931a05 Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Tue, 8 Jan 2019 16:08:02 +0100 Subject: Added author and update on editor --- _posts/2017-03-07-golang-profiling-simplified.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 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 2b5a262..4c7266c 100644 --- a/_posts/2017-03-07-golang-profiling-simplified.md +++ b/_posts/2017-03-07-golang-profiling-simplified.md @@ -1,7 +1,9 @@ --- + layout: post title: Golang profiling simplified description: Golang profiling made easy + --- **Table of contents** @@ -9,9 +11,9 @@ description: Golang profiling made easy 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) + 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