Skip to content

perf(runtime): prepare refreshable registry address index for #10110 #10251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
proggeramlug wants to merge 2 commits into from
Closed

perf(runtime): prepare refreshable registry address index for #10110 #10251

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a380535
perf(runtime): prepare refreshable registry address index
Sep 14, 2026
4be2ada
docs: key registry index changelog to PR 10251
Sep 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions changelog.d/10251-registry-address-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
Prepare the address-index fix for #10110: allow each registry to size its Bloom
filter and add `RegistryAddrIndex`, which rebuilds its bits from live addresses
as registrations retire. Readers retain three atomic bit tests with no lock or
allocation. Existing symbol filters retain their 16-word width and hash positions.

Adapted from [proggeramlug/perry#1](https://github.com/proggeramlug/perry/pull/1).
Coverage includes the reported 644-address population, retirement, 20,000-address
churn, address reuse, and concurrent admissions/refreshes. Hash slices scale with
the chosen width so all three probes can use the entire array.

The canonical-wrapper subsystem is still absent from `main`, so this is its
prerequisite, not a claim of the campaign's measured CPU improvement on `main`.
When that subsystem lands, use `RegistryAddrIndex<256>` in
`native_handle/canonical.rs`, admit before publishing the identity, and retire
after all three removal paths: stale identity replacement, finalized identity
removal, and explicit retirement (after `finalize_once`). Keep the authoritative
wrapper validation after `may_contain`. Issue #10110 remains open for that wiring.
Loading
Loading