feat: parallelize requests by default #102
Merged
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.
Description
By default graphql-java does not create threads. The container may create separate threads for different requests, and some of our implementations create threads to parallelize within a data fetcher, but if multiple queries come in the same HTTP request (batch), each will be executed in serial on the same thread by default.
With this change, we use a configurable thread pool to hand off execution at the GQL query level, rather than the HTTP request level.
Testing
Tested E2E as well as adding UTs
Checklist: