-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Remove MemoryStreamFactory and replace with RecyclableMemoryStreamFactory #4502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
One of its use cases is also to benchmark/profile the recyclable memorystream factory against one that does not pool. I'm okay reinstating the class existence for folks for whom the memory characteristic of recyclable memory stream come as a surprise. We had tickets in the past where folks suspected a memory leak due to recyclable memorystreams buffers. In some cases it might also be preferable to have GC to be more aggressive (e.g cron tooling) |
I think reinstating is fine, lets just not use it internally. |
Closed in favor of: #4509 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The commit message should indicate that usages of MemoryStreamFactory
are replaced with RecyclableMemoryStreamFactory
(and that MemoryStreamFactory
is not removed)
…4502) Usages of MemoryStreamFactory are replaced with RecyclableMemoryStreamFactory, MemoryStreamFactory is kept in place for external use.
…4502) Usages of MemoryStreamFactory are replaced with RecyclableMemoryStreamFactory, MemoryStreamFactory is kept in place for external use.
The only usage of
MemoryStreamFactory
internally is withing tests/documentation.Removing these uses as its doubtful if use in this situation is worthwhile.
This does remove the
MemoryStreamFactory
implementation as well, so this is technically a breaking change, so could be made non-breaking by reinstating this class.