Introduce BenchmarkConfig
to selectively use config in benchmark
#414
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #412 - but basically the
Config
holdsinputs
and that can be a hell loat of data to send along with every benchmark.In a benchmark with 16 scenarios and huge inputs we now save ourselves copying that potentially huge data structure a whopping 16 times to our benchmarking processes for no reason whatsoever (the scenarios already hold the
input
).