Skip to content

slice3: make batch storage explicit - #2

Closed
waywardmonkeys wants to merge 6 commits into
mainfrom
slice3/allocation-discipline
Closed

slice3: make batch storage explicit#2
waywardmonkeys wants to merge 6 commits into
mainfrom
slice3/allocation-discipline

Conversation

@waywardmonkeys

Copy link
Copy Markdown
Contributor

Replace the allocation-hiding batch helpers with explicit reusable batch state across residency and atlas. ResidencyTracker::process_requests and AtlasCache::process_queued now take caller-owned batch/output storage, and AtlasPageRouter::candidate_pages writes into caller-provided candidate storage while best_page_for remains allocation-free.

Add the cachet_wind_tunnel Criterion benchmark crate for the slice-3 hot paths, update facade docs/examples/tests to the explicit API, and keep benchmark dependencies out of core crates.

Replace the allocation-hiding batch helpers with explicit reusable batch state across residency and atlas. `ResidencyTracker::process_requests` and `AtlasCache::process_queued` now take caller-owned batch/output storage, and `AtlasPageRouter::candidate_pages` writes into caller-provided candidate storage while `best_page_for` remains allocation-free.

Add the `cachet_wind_tunnel` Criterion benchmark crate for the slice-3 hot paths, update facade `docs/examples/tests` to the explicit API, and keep benchmark dependencies out of core crates.
@waywardmonkeys
waywardmonkeys deleted the slice3/allocation-discipline branch August 1, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant