Skip to content

Commit ca2ff0b

Browse files
committed
CONTRIBUTING: There's no --features with-nexmark.
I guess it once existed but has been removed. Signed-off-by: Ben Pfaff <blp@feldera.com>
1 parent b4241c9 commit ca2ff0b

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -194,21 +194,21 @@ Each benchmark has its own options and behavior, as outlined below.
194194
You can run the complete set of Nexmark queries, with the default settings, with:
195195

196196
```shell
197-
cargo bench --bench nexmark --features with-nexmark
197+
cargo bench --bench nexmark
198198
```
199199

200200
By default this will run each query with a total of 100 million events emitted at 10M per second (by two event generator threads), using 2 CPU cores for processing the data.
201201

202202
To run just the one query, q3, with only 10 million events, but using 8 CPU cores to process the data and 6 event generator threads, you can run:
203203

204204
```shell
205-
cargo bench --bench nexmark --features with-nexmark -- --query q3 --max-events 10000000 --cpu-cores 8 --num-event-generators 6
205+
cargo bench --bench nexmark -- --query q3 --max-events 10000000 --cpu-cores 8 --num-event-generators 6
206206
```
207207

208208
For further options that you can use with the Nexmark benchmark,
209209

210210
```shell
211-
cargo bench --bench nexmark --features with-nexmark -- --help
211+
cargo bench --bench nexmark -- --help
212212
```
213213

214214
An extensive blog post about the implementation of Nexmark in DBSP:

0 commit comments

Comments
 (0)