Open
Conversation
This is very general and doesn't know anything about the benchmark suites. This is intended to handle the configuration management of running benchmarks with specified settings.
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
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.
I've updated my benchmark running scripts and figured I might as well PR them.
Sample:
The actual run command (
~/runnersis a symlink to~/OptSched/util/runners):BENCHSUITE=plaidml python3.8 ~/runners/multirun.py -o ~/local-results/output/$(~/runners/datename) -L yes,no --with STATIC_NODE_SUPERIORITY=YES 2ND_PASS_ILP_NODE_SUPERIORITY_PRESERVING_OCCUPANCY=YES --with STATIC_NODE_SUPERIORITY=NO 2ND_PASS_ILP_NODE_SUPERIORITY_PRESERVING_OCCUPANCY=NO -- ~/run-plaidbench.py {{label}}.logs -b xceptionThis does two runs of the
~/run-plaidbench.pycommand, one with the first--with's settings, and one with the second--with's settings.It does require Python 3.8; Python 3.6 doesn't have
capture_outputon thesubprocess.run(...)command.I'll also probably rebase this to simplify the git history if we do want to merge this.