From f3e97fdba5e08ec4b02635a05c230c0ab0b4ecf3 Mon Sep 17 00:00:00 2001 From: Philip O'Toole Date: Wed, 23 Dec 2015 15:19:57 -0500 Subject: [PATCH] Update with memory profiling instructions [ci skip] --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6d6e929e42..f501df28b6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -214,11 +214,11 @@ For more information on `go vet`, [read the GoDoc](https://godoc.org/golang.org/ Profiling ----- -When troubleshooting problems with CPU or memory the Go toolchain can be helpful. You can start InfluxDB with CPU or memory profiling turned on. For example: +When troubleshooting problems with CPU or memory the Go toolchain can be helpful. You can start InfluxDB with CPU and memory profiling turned on. For example: ```sh # start influx with profiling -./influxd -cpuprofile influxd.prof +./influxd -cpuprofile influxdcpu.prof -memprof influxdmem.prof # run queries, writes, whatever you're testing # Quit out of influxd and influxd.prof will then be written. # open up pprof to examine the profiling data.