Document how to run a single benchmark #132
Merged
Conversation
This file contains hidden or 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
Contributor
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I have found that for my usage of yjit-bench where e.g. I want to benchmark TruffleRuby or more Ruby versions,
run_benchmarks.rbassumes way too much about the platform, which Rubies are benchmarked and more.OTOH a huge advantage of this repository/set of benchmarks is they are all extremely easy to run with just
ruby -Iharness benchmarks/some_benchmark.rbso I documented that. That's in fact I think much better than many other benchmarks suites, because it's so easy to run a benchmark and get started.And then one can of course build some fairly trivial scripts to run N/all benchmarks on M Rubies etc based on their needs.