From dccfee1cd05fe511669dc6a939913b8da44434f4 Mon Sep 17 00:00:00 2001 From: Hardanish Singh <61027578+Hardanish-Singh@users.noreply.github.com> Date: Tue, 13 Jan 2026 12:26:33 -0500 Subject: [PATCH] doc: clean up writing-and-running-benchmarks.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR-URL: https://github.com/nodejs/node/pull/61345 Reviewed-By: Colin Ihrig Reviewed-By: Luigi Pinca Reviewed-By: Matteo Collina Reviewed-By: Rafael Gonzaga Reviewed-By: Ulises Gascón --- .../writing-and-running-benchmarks.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/doc/contributing/writing-and-running-benchmarks.md b/doc/contributing/writing-and-running-benchmarks.md index ccffefd73f3..9f830bed668 100644 --- a/doc/contributing/writing-and-running-benchmarks.md +++ b/doc/contributing/writing-and-running-benchmarks.md @@ -43,16 +43,19 @@ By default, `wrk` will be used as the benchmarker. If it is not available, `autocannon` will be used in its place. When creating an HTTP benchmark, the benchmarker to be used should be specified by providing it as an argument: -`node benchmark/run.js --set benchmarker=autocannon http` - -`node benchmark/http/simple.js benchmarker=autocannon` +```bash +node benchmark/run.js --set benchmarker=autocannon http +node benchmark/http/simple.js benchmarker=autocannon +``` #### HTTPS benchmark requirements To run the `https` benchmarks, one of `autocannon` or `wrk` benchmarkers must be used. -`node benchmark/https/simple.js benchmarker=autocannon` +```bash +node benchmark/https/simple.js benchmarker=autocannon +``` #### HTTP/2 benchmark requirements @@ -60,7 +63,9 @@ To run the `http2` benchmarks, the `h2load` benchmarker must be used. The `h2load` tool is a component of the `nghttp2` project and may be installed from [nghttp2.org][] or built from source. -`node benchmark/http2/simple.js benchmarker=h2load` +```bash +node benchmark/http2/simple.js benchmarker=h2load +``` ### Benchmark analysis requirements