Skip to content

🤖 Update Benchmark Results - #6626

Merged
thomhurst merged 1 commit into
mainfrom
automated-benchmarks-update
Aug 17, 2026
Merged

🤖 Update Benchmark Results#6626
thomhurst merged 1 commit into
mainfrom
automated-benchmarks-update

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

Automated Benchmark Update

This PR updates the benchmark documentation with the latest results from the Speed Comparison workflow.

Benchmarks Produced

Individual benchmark artifacts are available for download:

  • benchmark-DataDrivenTests
  • benchmark-AsyncTests
  • benchmark-ScaleTests
  • benchmark-MatrixTests
  • benchmark-MassiveParallelTests
  • benchmark-SetupTeardownTests
  • benchmark-BuildTime
  • benchmark-summary (aggregated overview)

Runtime Benchmarks

  • AsyncTests
  • DataDrivenTests
  • MassiveParallelTests
  • MatrixTests
  • ScaleTests
  • SetupTeardownTests

Build Benchmarks

  • BuildTime
  • 2026-08-17
  • Ubuntu Latest • .NET SDK 10.0.400

Changes

  • Updated benchmark data in docs/static/benchmarks/latest.json
  • Updated historical trends in docs/static/benchmarks/historical.json
  • Regenerated benchmark documentation in docs/docs/benchmarks/index.md
  • Updated benchmark summary in docs/static/benchmarks/summary.json

Workflow Run

  • Run ID: 32034699068
  • Triggered: workflow_dispatch
  • Date:

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

@thomhurst thomhurst added automated benchmarks documentation Improvements or additions to documentation ignore-for-release labels Aug 17, 2026
@thomhurst
thomhurst merged commit 64d8328 into main Aug 17, 2026
12 of 14 checks passed
@thomhurst
thomhurst deleted the automated-benchmarks-update branch August 17, 2026 16:25
@greptile-apps

greptile-apps Bot commented Aug 17, 2026

Copy link
Copy Markdown

Greptile Summary

This automated update refreshes the published runtime and build benchmark results for 2026-08-17.

  • Updates per-scenario JSON, aggregate benchmark data, generated Markdown tables and charts, and README figures.
  • Adds xUnit v3 AOT results to all six runtime benchmark datasets.
  • Advances the retained benchmark history and associated timestamps.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking benchmark-presentation inconsistency around the newly added xUnit v3 AOT results.

The benchmark data remains structurally consistent, but existing generated surfaces omit or display the new xUnit3_AOT method inconsistently.

Files Needing Attention: docs/static/benchmarks/latest.json, README.md, and generated benchmark pages

Important Files Changed

Filename Overview
docs/static/benchmarks/latest.json Refreshes aggregate benchmark values and adds xUnit3_AOT rows, but the new method is not consistently supported by presentation consumers.
README.md Refreshes headline benchmark values but continues to omit the newly available xUnit v3 AOT results.
docs/docs/benchmarks/engine/AsyncTests.md Regenerates the detailed benchmark page and exposes the new AOT result under its internal xUnit3_AOT identifier.
docs/static/benchmarks/historical.json Appends the latest date and evicts the oldest entry according to the established 90-entry retention behavior.

Reviews (1): Last reviewed commit: "chore: update benchmark results" | Re-trigger Greptile

Comment on lines +50 to +56
{
"Method": "xUnit3_AOT",
"Version": "4.0.0",
"Mean": "128.7 ms",
"Error": "1.05 ms",
"StdDev": "0.87 ms",
"Median": "128.5 ms"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Inconsistent xUnit AOT presentation

The new xUnit3_AOT method is not represented consistently across benchmark consumers: the README omits it despite claiming coverage across every framework, while detailed pages and interactive charts expose the internal identifier and lack the user-facing AOT treatment provided for TUnit.

Knowledge Base Used: Benchmarks and the Docusaurus Docs Site

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@claude

claude Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Code review

No issues found. This is an automated, data-only PR that regenerates benchmark results (docs/static/benchmarks/*.json) and their derived Markdown/README output from the Speed Comparison workflow — no source/logic changes to review. Skipped the full bug-hunt/CLAUDE.md-compliance pipeline since there's no application code in the diff to audit. Note: PR is already merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated benchmarks documentation Improvements or additions to documentation ignore-for-release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant