@@ -23,8 +23,8 @@ There are three ways to run benchmark tests:
|
23 | 23 | |
24 | 24 | For example, buffers: |
25 | 25 | |
26 | | -```sh |
27 | | -iojs benchmark/common.js buffers |
| 26 | +```bash |
| 27 | +node benchmark/common.js buffers |
28 | 28 | ``` |
29 | 29 | |
30 | 30 | The above command will find all scripts under `buffers` directory and require |
@@ -87,8 +87,8 @@ The last number is the rate of operations. Higher is better.
|
87 | 87 | |
88 | 88 | For example, buffer-slice.js: |
89 | 89 | |
90 | | -```sh |
91 | | -iojs benchmark/buffers/buffer-read.js |
| 90 | +```bash |
| 91 | +node benchmark/buffers/buffer-read.js |
92 | 92 | ``` |
93 | 93 | The output: |
94 | 94 | ``` |
@@ -104,8 +104,8 @@ This example will run only the first type of url test, with one iteration.
|
104 | 104 | (Note: benchmarks require __many__ iterations to be statistically accurate.) |
105 | 105 | |
106 | 106 | |
107 | | -```sh |
108 | | -iojs benchmark/url/url-parse.js type=one n=1 |
| 107 | +```bash |
| 108 | +node benchmark/url/url-parse.js type=one n=1 |
109 | 109 | ``` |
110 | 110 | Output: |
111 | 111 | ``` |
|