Optimize LoggingStream. #142
Open
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
davidfowl
reviewed
Mar 15, 2022
| @@ -24,26 +27,36 @@ public static async Task Main(string[] args) | |||
|
|
|||
| services.AddSignalR(); | |||
|
|
|||
| services.TryAddSingleton<ObjectPoolProvider, DefaultObjectPoolProvider>(); | |||
There was a problem hiding this comment.
This feels like an unnecessary dependency
There was a problem hiding this comment.
You mean using the String builder pool?
There was a problem hiding this comment.
The LoggingStream creates two new StringBuilders for every message that it logs. Why wouldn't you optimized that?
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.
Optimization of the
LoggingStream.StringBuilderPool.inkeyword.charinstead of astringwhen appending to theStringBuilder.Clean and conflict free version of #134