From 9cdfbb2927ca91639f097e21aba2cf131c38a3ed Mon Sep 17 00:00:00 2001 From: Weihan Li Date: Wed, 6 Sep 2023 23:00:41 +0800 Subject: [PATCH] update LOH threshold (#30252) --- aspnetcore/fundamentals/best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/fundamentals/best-practices.md b/aspnetcore/fundamentals/best-practices.md index f60233c904..0150eb9d7e 100644 --- a/aspnetcore/fundamentals/best-practices.md +++ b/aspnetcore/fundamentals/best-practices.md @@ -211,7 +211,7 @@ Use `HttpContext.Request.ReadFormAsync` instead of `HttpContext.Request.Form`. ## Avoid reading large request bodies or response bodies into memory -In .NET, every object allocation greater than 85 KB ends up in the large object heap ([LOH](https://blogs.msdn.microsoft.com/maoni/2006/04/19/large-object-heap/)). Large objects are expensive in two ways: +In .NET, every object allocation greater than or equal to 85,000 bytes ends up in the [large object heap (LOH)](/dotnet/standard/garbage-collection/large-object-heap). Large objects are expensive in two ways: * The allocation cost is high because the memory for a newly allocated large object has to be cleared. The CLR guarantees that memory for all newly allocated objects is cleared. * LOH is collected with the rest of the heap. LOH requires a full [garbage collection](/dotnet/standard/garbage-collection/fundamentals) or [Gen2 collection](/dotnet/standard/garbage-collection/fundamentals#generations).