Repository navigation
Worker Lifecycle
Sudhanshu edited this page Nov 11, 2026
·
1 revision
-
spawnavoids reusing a potentially unsafe CUDA context afterfork. -
torch.cuda.set_device(index)runs in CUDA workers; CPU workers set a per-process thread count. - Each worker reports readiness via
result_queue, waits ongo_event, then consumes tasks untilNone. - Exceptions are reported as tracebacks; parent detects failed worker processes or timeouts.
- Parent
finallyblock terminates any remaining workers and closes queues.
stateDiagram-v2
[*] --> Spawned
Spawned --> Initializing
Initializing --> Ready: model loaded or mock setup
Initializing --> Error: exception
Ready --> Waiting: notify parent and await go_event
Waiting --> Processing: task_queue.get(batch)
Processing --> Processing: next batch
Processing --> Finished: task_queue.get(None)
Processing --> Error: exception
Finished --> [*]
Error --> [*]: error message on result queue
Parallel LLM Inference
- Home
- Getting Started
- Architecture
- Implementation
- Operations