Automate benchmark compilation report #171
Draft
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
JulianGCalderon
force-pushed
the
report-compilation
branch
from
fa366b1 to
62bf052
Compare
JulianGCalderon
requested review from
azteca1998,
edg-l,
fmoletta,
gabrielbosio,
igaray and
pefontana
as code owners
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.
Depends on #170.
Automates the generation of reports for compilation benchmarks.
Similar to #170.
The
benchmark_compilation.shscript saves all compilation stats into a single file, along with system information. Then, theplot_compilation_stats.pytakes this single file, and generates an HTML report.I also removed some of the pie plots from
plot_compilation_stats.py, as they didn't give any useful information, and it didn't make sense to add them to the report.