Keep using ThreadPoolExecutor but increase number of threads#199
Merged
domesticmouse merged 2 commits intogooglemaps:masterfrom Nov 23, 2016
Merged
Keep using ThreadPoolExecutor but increase number of threads#199domesticmouse merged 2 commits intogooglemaps:masterfrom
domesticmouse merged 2 commits intogooglemaps:masterfrom
Conversation
…o create as many threads as current available cores. This will allow many threads to execute calls. The problem is that it does not seem to grow/shrink based on the number of operations
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.
Instead of using the newWorkStealingPool we can change ThreadPoolExecutor to create as many threads as current available cores. This will allow many threads to execute calls. The problem is that it does not seem to grow/shrink based on the number of operations