Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Putting a cap on the number of threads a scheduler can create #3669

Merged
merged 3 commits into from
Aug 8, 2023
Merged

Putting a cap on the number of threads a scheduler can create #3669

merged 3 commits into from
Aug 8, 2023

Conversation

kevgliss
Copy link
Contributor

@kevgliss kevgliss commented Aug 7, 2023

No description provided.

@kevgliss kevgliss added the bug Something isn't working label Aug 7, 2023
forestmonster
forestmonster requested changes Aug 7, 2023
View reviewed changes
Copy link
Contributor

@forestmonster forestmonster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious about concurrent.futures.ThreadPoolExecutor, and if num_workers=100 has the potential to create a new bottleneck?

@Netflix Netflix deleted a comment from forestmonster Aug 8, 2023
@kevgliss kevgliss merged commit 28322d8 into master Aug 8, 2023
@kevgliss kevgliss deleted the bugfix/scheduler-processes branch August 8, 2023 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@forestmonster forestmonster forestmonster approved these changes

@wssheldon wssheldon wssheldon approved these changes

Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@kevgliss @forestmonster @wssheldon