Skip to content

Background read-only region creation#1919

Open
jmpesp wants to merge 1 commit intooxidecomputer:mainfrom
jmpesp:concurrent_read_only_clone
Open

Background read-only region creation#1919
jmpesp wants to merge 1 commit intooxidecomputer:mainfrom
jmpesp:concurrent_read_only_clone

Conversation

@jmpesp
Copy link
Copy Markdown
Contributor

@jmpesp jmpesp commented Apr 9, 2026

When the Crucible Agent is requested to create a read-only region from a remote Downstairs source, this currently blocks the worker thread as region creation is performed in the worker loop, and it cannot respond to other state changes.

This commit spawns region creation threads that the main worker thread can send requests to, and sends all read-only region creation requests there.

This builds on the previous work to separate the serialized on-disk types from the in-memory types: a Creating state is added to the in-memory type and used while this background creation is occurring.

When the Crucible Agent is requested to create a read-only region from
a remote Downstairs source, this currently blocks the worker thread as
region creation is performed in the worker loop, and it cannot respond
to other state changes.

This commit spawns region creation threads that the main worker thread
can send requests to, and sends all read-only region creation requests
there.

This builds on the previous work to separate the serialized on-disk
types from the in-memory types: a `Creating` state is added to the
in-memory type and used while this background creation is occurring.
@jmpesp jmpesp requested a review from leftwo April 9, 2026 01:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant