Reduce the memory footprint of ManagedWebSocket #52022
Merged
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.
While working on the websocket compression I noticed two things but decided to leave them after the feature was completed:
RandomNumberGenerator
, which could be replaced withRandomNumberGenerator.Fill
.ManagedWebSocket
class was creatingCancellationTokenSource
but never really used the cancellation part. Since continuations fromCancellationTokenSource.Cancel
are executed synchronously, the cancellation source could be replaced with a method.This reduced the memory footprint of a websocket without compression enabled from 752 bytes to 552 bytes.
//cc @CarnaViire @scalablecory