fix: force 4 tokio worker threads on client#11
Merged
mickvandijke merged 1 commit intoWithAutonomi:mainfrom Mar 30, 2026
Merged
fix: force 4 tokio worker threads on client#11mickvandijke merged 1 commit intoWithAutonomi:mainfrom
mickvandijke merged 1 commit intoWithAutonomi:mainfrom
Conversation
The default #[tokio::main] uses num_cpus worker threads. On small client VMs (1-2 vCPU), this gives only 1-2 worker threads. The NAT traversal poll() function does synchronous work (parking_lot locks, DashMap iteration) that blocks its worker thread. With only 1 worker, this freezes the entire runtime — timers stop, keepalives can't fire, and connections die silently, causing upload hangs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
mickvandijke
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
worker_threads = 4on the tokio runtime regardless of CPU count.cargo/config.tomlto.gitignoreOn small client VMs (1-2 vCPU), the default
num_cpusgives only 1-2 worker threads. The NAT traversalpoll()function does synchronous work (parking_lot locks, DashMap iteration) that blocks its worker thread. With only 1 worker, this freezes the entire runtime — timers stop, keepalives can't fire, and connections die silently, causing upload hangs.Test plan
🤖 Generated with Claude Code