daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update aspnetcore/performance/memory.md 

Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
pull/30202/head
Aditya Mandaleeka 2023-09-07 15:55:46 -07:00 committed by GitHub
parent d8fb91fe78
commit 4b6ef1d391
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/performance/memory.md
View File

@ -30,7 +30,7 @@ When an ASP.NET Core app starts, the GC:
The preceding memory allocations are done for performance reasons. The performance benefit comes from heap segments in contiguous memory.
### Note about calling GC.Collect
### GC.Collect caveats
In general, ASP.NET Core apps in production should **not** use [GC.Collect](xref:System.GC.Collect%2A) explicitly. Inducing garbage collections at sub-optimal times can decrease performance significantly.