Skip to content
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.

Sign up for GitHub

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

Jump to bottom

perf: improve allocations in OwinEnvironment #58916

Open
DeagleGross opened this issue Nov 13, 2024 · 0 comments · May be fixed by #58917
Open

perf: improve allocations in OwinEnvironment #58916

DeagleGross opened this issue Nov 13, 2024 · 0 comments · May be fixed by #58917
Assignees
@DeagleGross
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Perf

Comments

@DeagleGross
Copy link
Contributor

One of the internal teams reported testing plain ASP.NET vs ASP.NET with Owin, and they found a big loss in the RPC with the OWIN usage (much bigger difference than expected).

@deanward81 has found the improvement to make in OwinEnvironment, where there is a way to reduce multiple allocations per request.
@DeagleGross DeagleGross self-assigned this Nov 13, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions label Nov 13, 2024
@DeagleGross DeagleGross linked a pull request Nov 13, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DeagleGross DeagleGross

Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Perf
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

perf: improve allocations in OwinEnvironment DeagleGross/aspnetcore
1 participant
@DeagleGross