(feat): Using criterion benchmarking framework with simple compile benchmark #9630
+213
−0
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
|
This change is |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5 tasks
eytan-starkware
force-pushed
the
eytan_graphite/_feat_using_criterion_benchmarking_framework_with_simple_compile_benchmark
branch
from
c5c34f2 to
ac232c9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
Added benchmarking capabilities to the Cairo compiler using Criterion. This PR introduces a new benchmark for measuring compilation performance, starting with a simple Fibonacci example.
Type of change
Please check one:
Why is this change needed?
To establish a baseline for measuring compiler performance and track improvements over time. This will help identify performance regressions and validate optimization efforts in the compilation pipeline.
What was the behavior or documentation before?
The project lacked structured benchmarking for the compiler, making it difficult to quantify performance changes between versions.
What is the behavior or documentation after?
The compiler now has a Criterion-based benchmark that measures compilation time for a Fibonacci example. This provides a foundation for adding more complex benchmarks and tracking performance metrics over time.
Additional context
The benchmark is configured with a smaller sample size (10) to balance accuracy with reasonable execution time. More benchmark cases can be added in the future to cover different compilation scenarios.