aboutsummaryrefslogtreecommitdiff
path: root/_posts/2017-03-07-golang-profiling-simplified.md
diff options
context:
space:
mode:
Diffstat (limited to '_posts/2017-03-07-golang-profiling-simplified.md')
-rw-r--r--_posts/2017-03-07-golang-profiling-simplified.md9
1 files changed, 9 insertions, 0 deletions
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
4description: Golang profiling made easy 4description: Golang profiling made easy
5--- 5---
6 6
7**Table of content**
8
9- [Where are my pprof files?](#where-are-my-pprof-files)
10- [Why is my cpu profile empty?](#why-is-my-cpu-profile-empty)
11- [Profiling](#profiling)
12 - [Memory profiling](#memory-profiling)
13 - [CPU profiling](#cpu-profiling)
14 - [Generating profiling reports](#generating-profiling-reports)
15
7Many 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. 16Many 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.
8 17
9Nevertheless, after searching and experimenting I have found a solution that works for me and probably should also for you. 18Nevertheless, after searching and experimenting I have found a solution that works for me and probably should also for you.