Reduce Prefetch Limit for PagedIterable and IterableStream#6538
Merged
alzimmermsft merged 4 commits intoNov 25, 2019
Merged
Conversation
alzimmermsft
requested review from
hemanttanwar,
jianghaolu and
srnagar
as code owners
November 25, 2019 20:39
srnagar
approved these changes
Nov 25, 2019
JonathanGiles
approved these changes
Nov 25, 2019
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.
Reduces scope of #6518
PagedIterableandIterableStreamwere updated to use the prefetch overload oftoIterableandtoStream, a prefetch of1is used instead of the default of256. This change reduces the scope of issue #6518 which saw eager retrieval of the next256pages or number of paged responses, whichever is less.