Use dedicated threads for background workers#151
Merged
ogaca-dd merged 1 commit intoDataDog:masterfrom Apr 14, 2021
kevingosse:kevin/statsdthread
Merged
Use dedicated threads for background workers#151ogaca-dd merged 1 commit intoDataDog:masterfrom kevingosse:kevin/statsdthread
ogaca-dd merged 1 commit intoDataDog:masterfrom
kevingosse:kevin/statsdthread
Conversation
lucaspimentel
approved these changes
Mar 31, 2021
This was referenced Mar 31, 2021
Contributor
|
@kevingosse: Thanks for the improvement! |
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
3 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.
Long-running operations (> 500 ms) should always go to a dedicated thread.
I used to think it didn't matter much, but I just ran into a situation where the threadpool wasn't scaling properly, and keeping this threadpool worker just to wait on a queue was causing a significant drop in a throughput.