diff options
| author | Nikolai Vavilov <vvnicholas@gmail.com> | 2017-02-10 23:21:35 +0300 |
|---|---|---|
| committer | Italo A. Casas <me@italoacasas.com> | 2017-02-14 19:52:30 +0300 |
| commit | 5059b6fcee4f90d77a6905bba82e384f898425ce (patch) | |
| tree | 0229a4856485d647ea2e05a7fadb38ec3df32bd5 /benchmark | |
| parent | 2333cd315546d66d797581d211dde685658377fa (diff) | |
benchmark: fix typos
PR-URL: https://github.com/nodejs/node/pull/11287
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Diffstat (limited to 'benchmark')
| -rw-r--r-- | benchmark/README.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/benchmark/README.md b/benchmark/README.md index 8796e1e7b6a..d1233470757 100644 --- a/benchmark/README.md +++ b/benchmark/README.md @@ -22,7 +22,7 @@ either [`wrk`][wrk] or [`autocannon`][autocannon]. path, hence if you want to compare two HTTP benchmark runs make sure that the Node version in the path is not altered. -`wrk` may be available through your preferred package manger. If not, you can +`wrk` may be available through your preferred package manager. If not, you can easily build it [from source][wrk] via `make`. By default `wrk` will be used as benchmarker. If it is not available @@ -55,8 +55,8 @@ In the event you get a message that you need to select a CRAN mirror first. You can specify a mirror by adding in the repo parameter. -If we used the "http://cran.us.r-project.org" mirror, it could look somehting like -this: +If we used the "http://cran.us.r-project.org" mirror, it could look something +like this: ```R install.packages("ggplot2", repo="http://cran.us.r-project.org") @@ -180,7 +180,7 @@ to be no improvements, then there shouldn't be any stars. **A word of caution:** Statistics is not a foolproof tool. If a benchmark shows a statistical significant difference, there is a 5% risk that this -difference doesn't actually exists. For a single benchmark this is not an +difference doesn't actually exist. For a single benchmark this is not an issue. But when considering 20 benchmarks it's normal that one of them will show significance, when it shouldn't. A possible solution is to instead consider at least two stars (`**`) as the threshold, in that case the risk |