OpenDevicePartnership / OpenDevicePartnership/odp-platform-common

Microbench `BootOrchestrator::execute()` end-to-end (mocked)

Open
#124 1 comment 0 reactions 1 assignee View on GitHub

@kat-perez is already working on this.

Since Jun 26, 2026.

Dominant language
Rust
Stars
1
Forks
5
Avg merge
3d 4h
Merged PRs (30d)
9

Description

Add a criterion microbenchmark covering the full BootOrchestrator::execute() path against mocked BootServices and RuntimeServices. Reports total cycles for the happy-path BDS sequence.

Why

The headline number for patina_boot perf. Lets us cite a single figure ("execute() takes N cycles") instead of diving into per-primitive detail. Comparing this number against the C BdsDxe equivalent is the simplest perf claim we can make to OEMs.

Acceptance criteria

  • cargo bench --bench orchestrator runs and emits cycle counts for execute() (happy path, mocked deps)
  • Output uses --output-format bencher so it's parseable by benchmark-action/github-action-benchmark
  • Bench is wired into the PR-comment workflow once #122 lands

Dependencies

  • Blocked by: #115 (bench harness scaffolding must exist first)
  • Blocks: #122 (PR-comment workflow has nothing to display until at least one bench exists)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.