🤖 Update Mock Benchmark Results

[thomhurst]

Automated Mock Benchmark Update

This PR updates the mock benchmark documentation with the latest results from the Mock Benchmarks workflow.

Benchmarks Produced

Individual benchmark artifacts are available for download:

• mock-benchmark-MockCreation
• mock-benchmark-Setup
• mock-benchmark-Invocation
• mock-benchmark-Verification
• mock-benchmark-Callback
• mock-benchmark-CombinedWorkflow
• mock-benchmark-summary (aggregated overview)

Libraries Compared

Libraries are discovered dynamically from the benchmark output. See the generated summary.json for the full list.

Changes

• Updated mock benchmark data in docs/static/benchmarks/mocks/latest.json
• Regenerated mock benchmark documentation in docs/docs/benchmarks/mocks/
• Updated mock benchmark summary in docs/static/benchmarks/mocks/summary.json

Workflow Run

• Run ID: 26430134729
• Triggered: schedule

---

🤖 This PR was automatically created and will be merged automatically once CI checks pass.

[claude]

Automated Benchmark Update Review

This is a routine automated data refresh — no functional code changes, just updated benchmark numbers and timestamps. The automation plumbing looks correct: JSON data files, rendered Markdown tables, and Mermaid chart axis ranges are all consistently updated together.

Notable observation: CombinedWorkflow regression

The CombinedWorkflow benchmark shows a notable day-over-day increase for TUnit.Mocks:

Run	Mean
2026-05-25	1.459 μs
2026-05-26	1.865 μs

That's a ~28% increase in a single day on the same environment. The other benchmarks are relatively stable (sub-5% variance), so this stands out. It's almost certainly CI runner noise — cloud VMs are notoriously inconsistent for microbenchmarks — but if this kind of variance is common in the combined workflow, it may be worth investigating whether the benchmark is running with [IterationTime]/warmup counts sufficient to stabilize results on shared runners.

Suggestion (not blocking)

If day-to-day variance in the combined benchmark continues to be this high, consider either:

• Increasing iteration count for the CombinedWorkflow benchmark specifically, or
• Running benchmarks on self-hosted or dedicated hardware to reduce runner noise

The relative ranking of libraries hasn't changed meaningfully, so this is fine to merge as-is. ✅

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}