Improve StreamingHub's grouping writer #416
Merged
Conversation
This file contains 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
AntonC9018
pushed a commit
to AntonC9018/MagicOnion
that referenced
this pull request
Sep 13, 2022
…rmance Improve StreamingHub's grouping writer
AntonC9018
pushed a commit
to AntonC9018/MagicOnion
that referenced
this pull request
Sep 13, 2022
…rmance Improve StreamingHub's grouping writer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When server is under heavy-load, StreamingHub's grouping writer's lock (
Group.WriteInAsyncLockVoid) causes a race condition.AsyncLock(SemaphoreSlim) creates many task-completion linkedlist node, it causes similar to memory leak.This huge number of locks, the server will not be able to recover even if the high load condition is resolved.
This PR removes
AsyncLockand write underChannel.