πββοΈ Add auto-generated small benchmarks on merge #38
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
This PR implements auto-generated small benchmarks that run on every merge into the
grainchainrepo, as requested. The system now supports a dual benchmark architecture:πββοΈ Small Benchmarks (New - Auto on Merge)
mainlocal,e2bbenchmarks/configs/merge-small.json㪠Comprehensive Benchmarks (Existing - Manual/Scheduled)
local,e2b,daytona,morphChanges Made
New Files
.github/workflows/merge-benchmark.yml- New workflow that triggers on PR mergesbenchmarks/configs/merge-small.json- Lightweight config with 10 iterationsModified Files
.github/workflows/benchmark.yml- Renamed to "Comprehensive Benchmarks" for clarityREADME.md- Updated documentation to explain the dual benchmark systemKey Features
β Merge-triggered: Runs automatically when PRs are merged to main
β Fast execution: 10 iterations per provider for quick feedback
β PR comments: Automatically posts benchmark results as PR comments
β Artifact storage: Results saved as GitHub Actions artifacts
β Git integration: Results committed back to repo for tracking
β Manual testing: Supports
workflow_dispatchfor manual testingTesting
The workflow can be tested manually using the "Run workflow" button in GitHub Actions, or will automatically trigger on the next PR merge.
Compliance
π» View my work β’ About Codegen