fix: use single-threaded tokio runtime in sccache (dist-)client#2704
Open
AJIOB wants to merge 2 commits into
Open
fix: use single-threaded tokio runtime in sccache (dist-)client#2704AJIOB wants to merge 2 commits into
AJIOB wants to merge 2 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2704 +/- ##
==========================================
- Coverage 74.51% 74.50% -0.01%
==========================================
Files 70 70
Lines 39652 39666 +14
==========================================
+ Hits 29546 29554 +8
- Misses 10106 10112 +6 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
AJIOB
changed the title
AJIOB
force-pushed
the
single-threaded-client
branch
2 times, most recently
from
15cec8f to
741976e
Compare
AJIOB
force-pushed
the
single-threaded-client
branch
3 times, most recently
from
a69e52a to
ff6010e
Compare
The sccache client was using Runtime::new() which creates a multi-threaded tokio runtime with worker threads equal to the number of CPU cores. On high-core-count servers running many parallel builds, this created an excessive number of threads. For example: - 96 vCPU server - 10 concurrent make invocations - Each make using -j16 - Result: 96 × 10 × 16 = 15,360 threads created by sccache wrappers While these threads are short-lived, with continuous build pipelines this constant thread creation/destruction causes unnecessary overhead. The sccache client only performs simple I/O operations (connecting to server, sending requests, receiving responses) and doesn't need worker threads. This change replaces all client-side Runtime::new() calls with Builder::new_current_thread().enable_all().build() to use a single-threaded runtime, reducing thread count from num_cpus to 1 per client invocation.
AJIOB
force-pushed
the
single-threaded-client
branch
from
ff6010e to
f02ffc5
Compare
Contributor
Author
|
Hi @sylvestre , Is it ok to you? I don't think we can add some useful testing for that changes. |
sylvestre
reviewed
Jun 6, 2026
Collaborator
|
and please udpate the commit message to explain the why |
The sccache client was using Runtime::new() which creates a multi-threaded tokio runtime with worker threads equal to the number of CPU cores. On high-core-count servers running many parallel builds, this created an excessive number of threads. For example: - 96 vCPU server - 10 concurrent make invocations - Each make using -j16 - Result: 96 × 10 × 16 = 15,360 threads created by sccache wrappers While these threads are short-lived, with continuous build pipelines this constant thread creation/destruction causes unnecessary overhead. The sccache client only performs simple I/O operations (connecting to server, sending requests, receiving responses) and doesn't need worker threads. This change replaces all dist-client-side Runtime::new() calls with Builder::new_current_thread().enable_all().build() to use a single-threaded runtime, reducing thread count from num_cpus to 1 per client invocation. The changes are inspired by the previous commit for the classic client.
AJIOB
force-pushed
the
single-threaded-client
branch
from
f02ffc5 to
570df28
Compare
Contributor
Author
|
@sylvestre , done, thanks |
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
4 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.
It's the #2460 follow-up with
dist-clientsimilar fixes.Thanks, @venkyt-arista, for the original fix