From 32dec82c13924152d907c44948ff618892c22c22 Mon Sep 17 00:00:00 2001 From: Aditya Mandaleeka Date: Wed, 30 Aug 2023 18:07:56 -0700 Subject: [PATCH] Typo fix. --- aspnetcore/performance/memory.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/performance/memory.md b/aspnetcore/performance/memory.md index 4ebea75c5c..1623a48d6c 100644 --- a/aspnetcore/performance/memory.md +++ b/aspnetcore/performance/memory.md @@ -215,7 +215,7 @@ The same leak could happen in user code, by one of the following: * Not releasing the class correctly. * Forgetting to invoke the `Dispose` method of the dependent objects that should be disposed. -### Large objects heap +### Large object heap Frequent memory allocation/free cycles can fragment memory, especially when allocating large chunks of memory. Objects are allocated in contiguous blocks of memory. To mitigate fragmentation, when the GC frees memory, it tries to defragment it. This process is called **compaction**. Compaction involves moving objects. Moving large objects imposes a performance penalty. For this reason the GC creates a special memory zone for *large* objects, called the [large object heap](/dotnet/standard/garbage-collection/large-object-heap) (LOH). Objects that are greater than 85,000 bytes (approximately 83 KB) are: