Re-measure O0 baseline and RockClimb 64x unroll - #91
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Re-runs the two measurements the paper still had marked as unverified.
Uninstrumented O0 baseline (
results/uninstrumentedO0.csv)All 13 benchmarks,
ckpt bench uninstrumentedO0. Geometric mean of O0/O3execution time is 2.56x (previously reported as 3.24x), ranging from
1.13x (sensor_fusion) to 10.81x (aes).
RockClimb
crcwith 64x unroll (results/rockclimb_crc_unroll64.csv)ckpt bench rockclimb crc --cap 10uF --max-unroll 64. Execution time dropsfrom 49373.11 to 31298.09 us (37% faster, previously 21%) and runtime
region boundary hits from 1593 to 69. Still 5% slower than Bao
(29813.37 us, previously 13%), and faster than Schematic-O3 (37679.71 us),
so the paper's claim holds.