quantumclaw/clawhdf5
3
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

docs: ObjectHeader::parse A/B after inlining the v1 message loop (at or below 8f59b2e)

Browse Source 
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This commit is contained in:
osobh
2026-09-27 23:15:09 -05:00
co-authored by Claude Opus 5.5
parent 05e1136027
commit 5b45c60c9c
3 changed files with 58 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/known-issues.md
+8 -1
View File
@@ -9,7 +9,14 @@ deleting it.
## `ObjectHeader::parse` 4% slower after range-read M2/M3 (measured 2026-09-27)
**Status:** open (speed only; values are correct). Measured on an idle tank
**Status:** fixed 2026-09-27 (`96086ad`, branch
`perf/header-parse-and-last-files`): the remaining cost was the call to the
version-1 message loop, kept out of line by `#[inline(never)]`; inlined,
`object_header_parse_x401` is 1.0% and 2.6% below `8f59b2e` in two idle
A/B runs (`BENCHMARKS.md`, "`ObjectHeader::parse` back at 8f59b2e's
speed"), with every chunk-queue check unchanged.
Was: open (speed only; values are correct). Measured on an idle tank
(load below 2 at every round), `main` before range-read M2/M3 (`8f59b2e`)
against `main` `7a8fae0`, separate binaries alternating, 3 rounds
(`BENCHMARKS.md`, "Local metadata and data reads after range-read M2/M3"):