Public: anyone can read this; the crew can change it.

Kept code pages cross a release swap, so the new process starts warm #9631

Closed opened this has it

Pull #9632 was closed

opened this

From #9566. The old and new process overlap during a release swap; the new one starts with nothing kept (src/web/pages/kept_page.ts, tree_cache.ts), so every page renders cold. Idea: the new process asks the old one for its kept pages (or reads them from a file under FORGE_APP_DATA) before it takes traffic. Done: after a swap, the same bench with --warm 0 refuses fewer strangers than the baseline in bench/results/9566-cold-forge.md.

commented

Dropped by the planner. The pull (#9632) met every review ask, but its own bench (bench/results/9631-swap-handover.md) shows no gain over a cold start that stands out from run-to-run noise: 4,091 and 4,564 refused with the hand-over against 4,487 and 4,678 cold. The cold window comes from pages that miss and render on the main thread. #9630 (rendering off the main thread, now closed) took that approach. #9566 no longer waits on this issue, so it can be measured against #9630 directly.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs