From 776ac9c64e537741f965de46f347dc4639c32bd6 Mon Sep 17 00:00:00 2001
From: Peter Marton <peter@risingstack.com>
Date: Wed, 11 Oct 2017 10:15:49 +0200
Subject: [PATCH] doc: add managing multiple builds section to benchmarking
 guide

---
 doc/guides/writing-and-running-benchmarks.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/guides/writing-and-running-benchmarks.md b/doc/guides/writing-and-running-benchmarks.md
index d418ed6974bf80..a6ac5206f6106d 100644
--- a/doc/guides/writing-and-running-benchmarks.md
+++ b/doc/guides/writing-and-running-benchmarks.md
@@ -163,6 +163,19 @@ First build two versions of Node.js, one from the master branch (here called
 `./node-master`) and another with the pull request applied (here called
 `./node-pr-5134`).
 
+To run multiple compiled versions in parallel you need to copy the output of the
+build: `cp ./out/Release/node ./node-master`. Check out the following example:
+
+```console
+$ git checkout master
+$ ./configure && make -j4
+$ cp ./out/Release/node ./node-master
+
+$ git checkout pr-5134
+$ ./configure && make -j4
+$ cp ./out/Release/node ./node-pr-5134
+```
+
 The `compare.js` tool will then produce a csv file with the benchmark results.
 
 ```console