From 26ec05cdbee032ffdb1936730ba9fbe65eacacff Mon Sep 17 00:00:00 2001
From: Hana Kim
Date: Wed, 13 Dec 2017 12:59:12 -0500
Subject: [PATCH] doc: update info about flame graphs in diagnostics.html
Use Brendan Gregg's FlameGraphs page link.
Mention the flame graph is available from the upstream pprof.
Change-Id: Ife1d5a5f4f93f20cd5952a09083f798b77d25a60
Reviewed-on: https://go-review.googlesource.com/83798
Reviewed-by: Brad Fitzpatrick
---
doc/diagnostics.html | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/diagnostics.html b/doc/diagnostics.html
index 8f5b59ecee..ea419d2c40 100644
--- a/doc/diagnostics.html
+++ b/doc/diagnostics.html
@@ -119,7 +119,7 @@ so it is recommended to collect only a single profile at a time.
The Go tools provide text, graph, and callgrind
-visualization of the profile data via
+visualization of the profile data using
go tool pprof
.
Read Profiling Go programs
to see them in action.
@@ -149,9 +149,11 @@ in the listing.
-Another way to visualize profile data is a flame graph.
+Another way to visualize profile data is a flame graph.
Flame graphs allow you to move in a specific ancestry path, so you can zoom
-in/out specific sections of code more easily.
+in/out of specific sections of code.
+The upstream pprof
+has support for flame graphs.