Allow specifying number of benchmarks in eval scripts #252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
filipeom
force-pushed
the
eval-sample
branch
3 times, most recently
from
c4f10ef to
08a428e
Compare
Due to the large cpu usage of the evaluation scripts we introduce a `-n` flag that allows specifying the number of benchmarks to use in each evaluation script. Thereby reducing the cpu usage of each script and producing an approximation of the real results
filipeom
force-pushed
the
eval-sample
branch
from
08a428e to
7cf92b0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to the large cpu usage of the evaluation scripts we introduce a
-nflag that allows specifying the number of benchmarks to use in each evaluation script. Thereby reducing the cpu usage of each script and producing an approximation of the real results