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
Add object pool for ServerSide RenderFrame serialization #5546
Labels
Milestone
Comments
SteveSandersonMS
referenced
this issue
in dotnet/blazor
Aug 16, 2018
SteveSandersonMS
referenced
this issue
in dotnet/blazor
Aug 16, 2018
SteveSandersonMS
referenced
this issue
in dotnet/blazor
Aug 16, 2018
SteveSandersonMS
referenced
this issue
in dotnet/blazor
Aug 21, 2018
…alization (#1329) * Eliminate temporary MemoryStream buffers used during RenderBatch serialization. Fixes #1132 * CR: Fix namespace
Reopening because we had to bring back the temporary buffer in #1666. |
SteveSandersonMS
referenced
this issue
in SteveSandersonMS/BlazorMigration
Nov 27, 2018
…alization (dotnet#1329) * Eliminate temporary MemoryStream buffers used during RenderBatch serialization. Fixes #1132 * CR: Fix namespace
aspnet-hello
added
area-mvc
Includes: MVC, Actions and Controllers, Localization, CORS, most templates
area-blazor
Includes: Blazor, Razor Components
labels
Dec 17, 2018
mkArtakMSFT
removed
area-mvc
Includes: MVC, Actions and Controllers, Localization, CORS, most templates
labels
May 9, 2019
This was addressed in 3.0. The rendering engine extensively uses ArrayPools |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Follow up item from #1116
We should consider pooling the byte arrays/streams from the render frame writer.
The text was updated successfully, but these errors were encountered: