bench: add ioxide 0.4.169 verbatim as an A/B reference - #1376
Closed
MDA2AV wants to merge 2 commits into
Closed
Conversation
baseline-4096 fell from 4,108,420 rps at 6401.5% CPU (0.4.169, 2026-08-09) to 3,896,541 at 5983.6% (0.7.211, 2026-08-28). Nothing distinguishes a library regression from a change in the machine, because no measurement exists for 0.7.210 on its own and the two runs are three weeks apart. This is the entry as it stood at cc794d0, restored file for file, so both can run back to back in one session. Same numbers as today's ioxide means the box moved; ~4.1M again means it is the library. Disabled: it never sends FIN on Connection: close, which is what #1289 disabled the live entry for and 0.7.210 fixed, so it does not pass validate.sh. benchmark.sh does not check enabled and the workflow's filter only applies to framework=all, so it still runs by name. Two deviations from verbatim: nuget.config drops the local developer feed for then-unpublished packages, and tests is trimmed to baseline and json since static, crud, api-4 and api-16 are no longer profiles. Claude-Session: https://claude.ai/code/session_016iyXstHcyyy1y47jAoBHid
Owner
Author
|
/benchmark -f ioxide-0-4-169 -t baseline |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
The first cut of this entry pinned ioxide at 0.4.169 and left the base image on the floating 11.0-preview tag, so both arms ran the same runtime. The old entry regressed as well, which says nothing about the library. That tag moved between the two measurements: 11.0.0-preview.6 published 2026-07-28 preview.6.26359.118 11.0.0-preview.7 published 2026-08-28 preview.7.26381.103 baseline-4096 was 4,108,420 on 2026-08-09, when 11.0-preview was preview.6, and 3,896,541 on 2026-08-28 -- the day preview.7 shipped. Both images are now pinned, through separate args because the repositories version differently: 11.0.100-preview.N for the SDK, 11.0.0-preview.N for the runtime. Verified in the built image: preview.6.26359.118, and it serves. Claude-Session: https://claude.ai/code/session_016iyXstHcyyy1y47jAoBHid
Owner
Author
|
/benchmark -f ioxide-0-4-169 -t baseline |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
baseline-4096 fell from 4,108,420 rps at 6401.5% CPU (0.4.169, 2026-08-09) to 3,896,541 at 5983.6% (0.7.211, 2026-08-28). Nothing distinguishes a library regression from a change in the machine, because no measurement exists for 0.7.210 on its own and the two runs are three weeks apart.
This is the entry as it stood at cc794d0, restored file for file, so both can run back to back in one session. Same numbers as today's ioxide means the box moved; ~4.1M again means it is the library.
Disabled: it never sends FIN on Connection: close, which is what #1289 disabled the live entry for and 0.7.210 fixed, so it does not pass validate.sh. benchmark.sh does not check enabled and the workflow's filter only applies to framework=all, so it still runs by name.
Two deviations from verbatim: nuget.config drops the local developer feed for then-unpublished packages, and tests is trimmed to baseline and json since static, crud, api-4 and api-16 are no longer profiles.
Claude-Session: https://claude.ai/code/session_016iyXstHcyyy1y47jAoBHid
Description
PR Commands — comment on this PR to trigger (requires collaborator approval):
/benchmark -f <framework>/benchmark -f <framework> -t <test>/benchmark -f <framework> --save/benchmark -f <framework> -t <test> --save/benchmark -f <framework> --compare <other>/benchmark-multiple -f <fw1>,<fw2>,...-tand--savetoo; saved results land in a single commit/benchmark-multiple --save-fneeded: benchmark and save every framework the PR touches/benchmark-test -t <test><test>and save the resultsFor
/benchmark, always specify-f <framework>; the flags combine in any order. Results come back as a comment with a per-profile table of RPS, p99, CPU and memory — one table per framework on multi runs. A new benchmark comment while a run is in flight queues behind it (one deep) instead of cancelling it. For multi-framework PRs (dependency bumps, same-language refactors) prefer/benchmark-multiple, which runs everything in a single job and commits all saved results together, so no run overwrites another.--compareworks on single-framework runs only.What the deltas are measured against. By default, this framework's own results published on
main- answering "did this change help?". When you are tuning a variant or a successor entry,--comparere-bases them on another entry instead:The reply states which baseline it used, and profiles the other framework does not run show
n/arather than a delta.Run benchmarks locally
You can validate and benchmark your framework locally with the lite script — no CPU pinning, fixed connection counts, all load generators run in Docker.
Requirements: Docker Engine on Linux. Load generators (gcannon, h2load, h2load-h3, wrk) are built as self-contained Docker images on first run.