Light Freshness Edit: ASP.NET - Performance#37106
Conversation
|
@tdykstra - Refreshed topics ready for your review. See top comment for details. Thanks |
| * 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. | ||
|
|
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
wadepickett
left a comment
There was a problem hiding this comment.
Reviewed. Found a few things to correct or consider. Overall, great work.
Co-authored-by: Wade Pickett <wpickett@microsoft.com>
tdykstra
left a comment
There was a problem hiding this comment.
Looks good, just a few comments and suggestions.
Co-authored-by: Tom Dykstra <tdykstra@microsoft.com>
|
@tdykstra @wadepickett - Updates applied. |
wadepickett
left a comment
There was a problem hiding this comment.
Approved. Great work. All items brought up in review have been addressed, thanks.

This PR contains light freshness updates to two articles:
moniker range=">= aspnetcore-6.0")For details, see ADO request 568764.
Internal previews