From 7f5b486e995257fc3233f75deacc3a7fb3c743a5 Mon Sep 17 00:00:00 2001
From: Philip O'Toole <philip.otoole@yahoo.com>
Date: Tue, 13 Oct 2015 15:23:07 -0700
Subject: [PATCH] More profiling help

[ci skip]
---
 CONTRIBUTING.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 83c59e8e85..4aa3f55cc7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -229,7 +229,8 @@ When troubleshooting problems with CPU or memory the Go toolchain can be helpful
 # start influx with profiling
 ./influxd -cpuprofile influxd.prof
 # run queries, writes, whatever you're testing
-# open up pprof
+# Quit out of influxd and influxd.prof will then be written.
+# open up pprof to examine the profiling data.
 go tool pprof influxd influxd.prof
 # once inside run "web", opens up browser with the CPU graph
 # can also run "web <function name>" to zoom in. Or "list <function name>" to see specific lines