Skip to content

doc: edit the benchmark guide #12041

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Trott wants to merge 2 commits into from
Closed

doc: edit the benchmark guide #12041

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6bdc2dd
doc: edit the benchmark guide
Trott Mar 25, 2017
88ccafc
squash: a -> an
Trott Mar 25, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
squash: a -> an
  • Loading branch information
@Trott
Trott committed Mar 25, 2017
commit 88ccafc5ce7f0b72d727845a9f92755e8613778a
2 changes: 1 addition & 1 deletion doc/guides/writing-and-running-benchmarks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Node.js version in the path is not altered.
easily build it [from source][wrk] via `make`.

By default, `wrk` will be used as the benchmarker. If it is not available,
`autocannon` will be used in its place. When creating a HTTP benchmark, you can
`autocannon` will be used in its place. When creating an HTTP benchmark, you can
specify which benchmarker should be used by providing it as an argument:

`node benchmark/run.js --set benchmarker=autocannon http`
Expand Down