-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[QUIC] Optimize stream reads #42651
Labels
Milestone
Comments
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Sep 23, 2020
Tagging subscribers to this area: @dotnet/ncl |
scalablecory
added
tenet-performance
Performance related issue
and removed
untriaged
New issue has not been triaged by the area owner
labels
Sep 23, 2020
28 tasks
Implementing this as part of #756 |
Closed
@CarnaViire was this fixed with your PR which scavenged Cory's PR? Can you close this in case of a YES, please? |
Yes, this was done in #55505 |
ghost
locked as resolved and limited conversation to collaborators
Aug 14, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The way we are implementing stream reads means we will often have more async/await overhead than is needed.
Instead of having an internal resettable task that we always await inside of
ReadAsync
, we should return a resettable task and have the MsQuic callback manage completing it. This will allow us to avoid an async state machine in ReadAsync().The text was updated successfully, but these errors were encountered: