oltpbenchmark / oltpbench

Database Benchmarking Framework
http://oltpbenchmark.com/
Other
401 stars 267 forks source link

Ambiguous mixed benchmark syntax #26

Open dedcode opened 11 years ago

dedcode commented 11 years ago

The work configuration syntax could be enhanced. Now, to specify an unlimited rate one has still to specify a non zero rate value. I suggest a versatile value for a work, disabled unlimited int_value for the <rate> entry, for example: 1- Applies to all benchmarks: <rate>100</rate> <rate>unlimited</rate> <rate>disabled</rate>

2- Applies to a specific benchmark (and overrides the global rate): <rate bench="tpcc">disabled</rate>

alendit commented 11 years ago

Hey,

there is no need for 3 different tags indeed, I'll look into it.

alendit commented 11 years ago

Merged my changes into the dimitri_dev branch.