Avoid allocations in BeginAsyncPacketRead #12039
Open
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.
Context
We can avoid a few allocations in the
BeginAsyncPacketRead()
path. There are repeated delegate creations that can be reused, and there is some state that is used inBodyReadComplete()
that we can get without allocating.There are ~40MB of allocations of
AsyncCallback
and ~10MB of Tuple allocations
We can avoid these allocations by reusing the delegates and storing the state that's used in
BodyReadComplete()
(just the packet length) as a field.Changes Made
Testing
Notes