Skip to content

Light Freshness Edit: ASP.NET - Performance#37106

Merged
wadepickett merged 6 commits intodotnet:mainfrom
GitHubber17:568764-j
May 7, 2026
Merged

Light Freshness Edit: ASP.NET - Performance#37106
wadepickett merged 6 commits intodotnet:mainfrom
GitHubber17:568764-j

Conversation

@GitHubber17
Copy link
Copy Markdown
Contributor

@GitHubber17 GitHubber17 commented May 5, 2026

This PR contains light freshness updates to two articles:

  • Memory management and garbage collection (GC) in ASP.NET Core
  • Response compression in ASP.NET Core (moniker range=">= aspnetcore-6.0")

For details, see ADO request 568764.


Internal previews

📄 File 🔗 Preview link
aspnetcore/performance/memory.md customer intent: As an ASP.NET developer, I want to understand memory management and garbage collection in ASP.NET Core, so I can manage memory in my apps.
aspnetcore/performance/response-compression.md Response compression in ASP.NET Core

@GitHubber17 GitHubber17 marked this pull request as ready for review May 6, 2026 18:23
@GitHubber17
Copy link
Copy Markdown
Contributor Author

@tdykstra - Refreshed topics ready for your review. See top comment for details. Thanks

Cc @cmastr @wadepickett

Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/response-compression.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
* GC drops from 300 MB to 10 MB

On a typical web server environment, CPU usage is more important than memory, therefore the Server GC is better. If memory utilization is high and CPU usage is relatively low, the Workstation GC might be more performant. For example, high density hosting several web apps where memory is scarce.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When an achor is removed, good to see what was using it. I checked and there were 7 articles using this "sc" anchor in this repo. I will create a seperate issue for that and take care of it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always check for anchor usage before removing, and update as needed. My results showed zero hits this time. Not sure why there was a discrepancy between your search and mine.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Copy link
Copy Markdown
Contributor

@wadepickett wadepickett May 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, that is great you check. Sorry, I realize now my comment implied it wasn't checked. I could have worded that in a better way.
The query I used was this:
https://github.com/search?q=repo%3Adotnet%2FAspNetCore.Docs%20performance%2Fmemory%23sc&type=code

Addressing those in #37116

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. I see now what I missed. I'm not used to links that leave off the file extension. In most other repos, the build validation detects broken bookmark links. Thanks for dbl-checking.

Copy link
Copy Markdown
Contributor

@wadepickett wadepickett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed. Found a few things to correct or consider. Overall, great work.

Co-authored-by: Wade Pickett <wpickett@microsoft.com>
Copy link
Copy Markdown
Contributor

@tdykstra tdykstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a few comments and suggestions.

Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
Comment thread aspnetcore/performance/response-compression.md Outdated
Comment thread aspnetcore/performance/response-compression.md Outdated
Comment thread aspnetcore/performance/memory.md Outdated
@tdykstra tdykstra changed the title Light Freshness Edit: ASP.NET - Performace Light Freshness Edit: ASP.NET - Performance May 7, 2026
GitHubber17 and others added 2 commits May 7, 2026 09:43
@GitHubber17
Copy link
Copy Markdown
Contributor Author

@tdykstra @wadepickett - Updates applied.

Copy link
Copy Markdown
Contributor

@wadepickett wadepickett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Great work. All items brought up in review have been addressed, thanks.

@wadepickett wadepickett merged commit 7d005bc into dotnet:main May 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants