Replace the local pool scaler with statically started threads - #478
Closed
hermabr wants to merge 1 commit into
Closed
Replace the local pool scaler with statically started threads#478hermabr wants to merge 1 commit into
hermabr wants to merge 1 commit into
Conversation
The dynamic scaler (scale thread, polling interval, failed-thread bookkeeping, restart budget, idle timeouts forcing workers to exit and be recreated) was built for the HTTP era when idle workers polled. An idle WebSocket worker is just a blocked thread, so start max_workers threads once, keep them connected with no idle timeout, and let the server closing the connection end them. A crashed worker thread now fails the run immediately: job failures are already caught inside the worker loop, so a thread-level crash means a furu bug, not a job problem. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Aug 1, 2026
hermabr
marked this pull request as ready for review
August 1, 2026 23:50
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
1 participant
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.
The dynamic scaler (scale thread, polling interval, failed-thread
bookkeeping, restart budget, idle timeouts forcing workers to exit and
be recreated) was built for the HTTP era when idle workers polled. An
idle WebSocket worker is just a blocked thread, so start max_workers
threads once, keep them connected with no idle timeout, and let the
server closing the connection end them.
A crashed worker thread now fails the run immediately: job failures are
already caught inside the worker loop, so a thread-level crash means a
furu bug, not a job problem.