aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHana Kim <hakim@google.com>2017-12-13 12:59:12 -0500
committerHyang-Ah Hana Kim <hyangah@gmail.com>2017-12-13 19:04:01 +0000
commit26ec05cdbee032ffdb1936730ba9fbe65eacacff (patch)
tree9fbf3e711aa57a17eafdc0dbd3678d4126399210
parent81c19cc0119d1b88e9cd26f65d93f3eede0d8620 (diff)
downloadgo-26ec05cdbee032ffdb1936730ba9fbe65eacacff.tar.xz
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 <bradfitz@golang.org>
-rw-r--r--doc/diagnostics.html8
1 files 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.
<p>
The Go tools provide text, graph, and <a href="http://valgrind.org/docs/manual/cl-manual.html">callgrind</a>
-visualization of the profile data via
+visualization of the profile data using
<code><a href="https://github.com/google/pprof/blob/master/doc/pprof.md">go tool pprof</a></code>.
Read <a href="https://blog.golang.org/profiling-go-programs">Profiling Go programs</a>
to see them in action.
@@ -149,9 +149,11 @@ in the listing.</p>
</p>
<p>
-Another way to visualize profile data is a <a href="https://github.com/uber/go-torch">flame graph</a>.
+Another way to visualize profile data is a <a href="http://www.brendangregg.com/flamegraphs.html">flame graph</a>.
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 <a href="https://github.com/google/pprof">upstream pprof</a>
+has support for flame graphs.
</p>
<p>