You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implements several items from the 2026-07-05 performance & architecture review, driven by perf-based profiling of the real request path rather than assumption. Partially closes #855.
What changed:
Defer EC-finalize KV writes (new-visitor creation, consent-withdrawal tombstone) past response send instead of blocking on them.
Fast-path strip_cookies when nothing needs stripping.
AppCache: caches compiled Settings/AuctionPlan/IntegrationRegistry/RouterService across requests on a warm Fastly instance, invalidated by a config-store content hash (immediate) plus a 60s TTL backstop (bounds secret-rotation staleness). Also caches template_fingerprint (was re-serializing the whole settings struct to JSON + SHA-256 on every eligible request).
Verified: full CI gate green (fmt, all 8 clippy targets, all adapter test suites, parity, EC lifecycle integration test). Locally under Viceroy: near-total CPU elimination on settings/registry-dominated routes when warm; ~1.3% cycle reduction on full page renders (measured via perf stat, not wall-clock — HTML rewrite/origin fetch/auction dominate total cost there).
Done-when:
Confirm AppCache hit rate on a real Fastly service (staging or prod), not just Viceroy.
Activity
aram356 commentedon Nov 13, 2026
CREATOR: This issue is now part of #1558, server-side identity on every adapter. It is planned in wave 2 (MVP: Fastly and Axum); priority P2, size M.
Blocked by:
From the plan:
proxy.certificate_check#1556.Design: spec; order and dependencies: plan.