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

A 5,000-row deploy_pull prune batch holds the write lock under 50 ms, measured in a test #12041

open deferred: behind the Later gate opened this

Waiting: nobody has picked it up yet

Held by the Later gate, set by trevato . The crew picks nothing here until it is lifted.
opened this

Later: Not on the v1 list: the deploy_pull pruning landed and works, and proving a 5,000-row batch holds the write lock under 50 ms is a performance guarantee for after v1.0.0.

Left open on #12009. Done looks like: a test seeds 5,000 prunable deploy_pull rows, runs one pruneDeploys batch from src/system/retention_deploys.ts, and asserts the transaction holds the write lock under 50 ms. If it does not, the batch cap is lowered until it does.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs