fix: increase max concurrent resolvers #1544
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.
Motivation and Context
Based on our observations in production and feedback from customers, we have concluded that the
ENGINE_MAX_CONCURRENT_RESOLVERS
value was set too low. Additionally, we have resolved a potential memory issue that we previously misattributed to this limit. A value that is too low can lead to increased latency in subgraph requests due to limited concurrency.Checklist