Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/actions/install-rust/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ runs:
steps:
- name: Install rust-toolchain.toml
shell: bash
run: rustup show
run: rustup toolchain install
- name: Install additional rustup components
if: inputs.components != ''
shell: bash
Expand Down
2 changes: 1 addition & 1 deletion skills/codspeed-setup-harness/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ Good benchmarks are representative, isolated, and stable. Here are guidelines:

- **Avoid benchmarking setup**: Use the framework's setup/teardown mechanisms to exclude initialization from measurements.

- **Prevent dead code elimination**: Use `black_box()` (Rust), `benchmark.pedantic()` (Python), or equivalent to ensure the compiler/runtime doesn't optimize away the work you're measuring.
- **Prevent dead code elimination**: Use `black_box()` (Rust), `benchmark::DoNotOptimize` (C++), or `Blackhole.consume` (JMH) so the compiler doesn't optimize away unused results.

- **Cover the critical path**: Benchmark the functions that matter most to your users — the ones called frequently or on the hot path.

Expand Down