feat: optimize receiving messages#158
Closed
unsafePtr wants to merge 1 commit into
Closed
Conversation
Marfusios
added a commit
that referenced
this pull request
May 13, 2026
Marfusios
added a commit
that referenced
this pull request
May 13, 2026
Merge the receive-path optimization from PR #158 and add further low-allocation improvements for pooled receive buffers, text-send encoding, cached observables, and binary message logging. Add a BenchmarkDotNet project with documented before/after results so receive buffering, text encoding, observable access, and response-message formatting can be measured repeatably.
Owner
|
@unsafePtr, sorry for the late response, just merged your commit today, thanks! |
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
2 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.
Background
scenarios. ArrayBufferWriter is more suitable for typical WebSocket message sizes. RecyclableMemoryStream is still used when the user explicitly requests to receive messages as streams (IsStreamDisposedAutomatically = false), maintaining backward compatibility.