Optimize dataloader fetching for lists #5989
Closed
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.
Dataloader currently have a issue with batching.
The first call to "LoadAsync" will initiate a
Schedule
on the batch dispatcher. In a specfic combination of cases, a fetch of a list of keys will lead to two fetches instead of one.What happens is the following. While we are iterating through all the requested keys, the first key will call schedule on the batch dispatcher. When we are calling
LoadAsync
from a mutation,Schedule
will immediately dispatch. We continue synchronously and enter reenter the lock of the dataloader that we arleady own. We immediatly fetch with just one key instead of all the keys.