-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable Task.WhenAll()
in all cases
#10914
Labels
breaking-change
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
punted-for-3.0
type-enhancement
Milestone
Comments
divega
changed the title
Consider removing code that serializes async queries
Consider removing code that serializes async queries executed concurrently
Feb 8, 2018
bricelam
added
consider-for-current-release
and removed
consider-for-current-release
labels
May 15, 2018
Remove in 3.0. |
ajcvickers
changed the title
Consider removing code that serializes async queries executed concurrently
Disable Mar 8, 2019
Task.WhenAll()
in all cases
Pulled this back in 3.0 since it was a product bug due to #12138 |
smitpatel
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Aug 7, 2019
smitpatel
added a commit
that referenced
this issue
Aug 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking-change
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
punted-for-3.0
type-enhancement
Currently we have guards in query code that allow multiple queries from the same
DbContext
get serialized when using Task.WhenAll(). We originally did this to work with some of the query operators in IX Async which consumed the async enumerables in parallel. We now think this may be introducing unnecessary overhead, plus customers actually using Task.WhenAll() directly aren't getting what they expect.This issue is about throwing when we find this scenario. It is a breaking change, but we believe it is worth considering. The code necessary to throw should have less overhead.
cc @anpete @ajcvickers @roji
The text was updated successfully, but these errors were encountered: