[evaluation] Add performance/resource usage evaluation script#779
Draft
[evaluation] Add performance/resource usage evaluation script#779
Conversation
Builds Dynamatic via ninja, then runs the embedded .dyn script for each kernel in parallel.
Archives each kernel's output directory after evaluation finishes.
Check for FATAL in stdout, and "C and VHDL outputs match" in sim/report.txt.
There are some issues with the default (4 ns) clock period. For example, histogram takes almost twice as many cycles for some reason when reducing the period from 5 ns to 4 ns.
MaxWipfli
force-pushed
the
mwipfli/eval-script
branch
from
1ef2c85 to
4611497
Compare
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.
This adds a pair of scripts to perform a full evaluation of Dynamatic on a fixed number of kernels from the integration tests. Compared to the GTest-based integration test flow, this also runs synthesis, and it is easier to control and change the
*.dynscript used. Also, there is a script to extract key figures (clock cycles, resource usage, critical path) into a CSV file for further processing.