Repository navigation
ci: Build CodSpeed benchmarks outside the simulation - #77
Conversation
CodSpeed's simulation mode runs the action's whole command under Valgrind, so compiling cargo-codspeed and the benchmarks there took ~40 minutes, against ~30 seconds for the benchmarks themselves.
Findings
|
There was a problem hiding this comment.
Actionable comments posted: 1

Review info
-
Run configuration-
- Source mode: Auto
- Repository: Unavailable
- Branch: Unavailable
- File: No configuration file from this repository applied
- Commit: Unavailable
- Layers: Organization UI
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
e5aebe8d-785d-413b-a90b-9e276792abd6
Files selected for processing: 2-
.github/workflows/codspeed.ymlMakefile
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
-
Merging this PR will not alter performance1 warning
Performance Changes
Comparing Footnotes
|
CodSpeed benchmarks take ~40 minutes since moving to simulation mode in #75.
Simulation mode runs the action's whole command under Valgrind, including installing
cargo-codspeed(5m30s) and compiling the benchmarks (33m), while the benchmarks themselves take ~30 seconds.Changes
cargo-codspeedand build the benchmarks in a step before the CodSpeed action, which now only runs them.make benchmarkintobenchmark-buildandbenchmark-run;make benchmarkstill does both.