Unverified Commit 4cbe8ce9 authored by vercel-fleet-prod[bot]'s avatar vercel-fleet-prod[bot] Committed by GitHub

Clarify unused state ID ranges in documentation

Co-authored-by: 's avatarLuke Sandberg <210140+lukesandberg@users.noreply.github.com>
parent d23fb5dc
...@@ -46,7 +46,7 @@ Values containing operations still require their usual call-graph connections. ...@@ -46,7 +46,7 @@ Values containing operations still require their usual call-graph connections.
Persistence writes only dirty state rows and collected-ID tombstones, atomically Persistence writes only dirty state rows and collected-ID tombstones, atomically
with affected task data and allocator progress. A fixed-bucket multi-value index with affected task data and allocator progress. A fixed-bucket multi-value index
tracks live IDs through individual insertions/deletions, without rewriting an tracks live IDs through individual insertions/deletions, without rewriting an
entire value store or scanning holes in the allocated ID range on restart. Task entire value store or scanning unused IDs in the allocated range on restart. Task
GC collects task-owned states; named roots pin their namespace, and normal GC GC collects task-owned states; named roots pin their namespace, and normal GC
aging applies after the last root drops. aging applies after the last root drops.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment