Merge pull request #8478 from MicrosoftDocs/main637989807062485099sync_temp

Repo sync for protected CLA branch

Author: Court72

docs/profiling/perf-insights-excessive-induced-gcs.md

@@ -0,0 +1,30 @@
+---
+title: Perf insights for excessive induced GCs
+description: Learn how to improve performance for excessive induced garbage collections
+ms.date: 9/15/2022
+ms.topic: reference
+author: mikejo5000
+ms.author: mikejo
+manager: jmartens
+ms.technology: vs-ide-debug
+ms.workload: 
+  - multiple
+---
+
+# Excessive induced GCs
+
+This article describes performance insights for excessive induced garbage collections (GCs).
+
+## Cause
+
+It's rarely justified inducing GCs because the garbage collector manages its own schedule. The only rare cases are mostly from the framework, but even that should be very rare. If you're seeing too many induced GCs, it's something to investigate, especially if you're worried about your GC time or if you're surprised by the fact there are induced GCs.
+
+## Rule description
+
+The [.NET Garbage Collector (GC)](/dotnet/standard/garbage-collection/) can determine the best time to perform a collection in most cases.
+
+When an application frequently forces GC collections, it might impact performance and responsiveness of an application.
+
+## How to investigate a warning
+
+Look for <xref:System.GC.Collect%2A> and check whether the method calls are really needed.

docs/profiling/perf-insights-high-loh-fragmentation.md

@@ -0,0 +1,28 @@
+---
+title: Perf insights for high LOH fragmentation
+description: Learn how to improve performance for high large object heap (LOH) fragmentation
+ms.date: 9/15/2022
+ms.topic: reference
+author: mikejo5000
+ms.author: mikejo
+manager: jmartens
+ms.technology: vs-ide-debug
+ms.workload: 
+  - multiple
+---
+
+# High LOH Fragmentation
+
+This article describes performance insights for high large object heap (LOH) allocations.
+
+## Cause
+
+The [large object heap (LOH)](/dotnet/standard/garbage-collection/large-object-heap) is not compacted and the fragmentation is used to satisfy LOH allocation requests. Consider reducing temporary large object allocations through reuse or pooling to avoid triggering frequent Gen2 GCs.
+
+## Rule description
+
+The [.NET Garbage Collector (GC)](/dotnet/standard/garbage-collection/) puts large objects in a specific region of memory known as the [large object heap (LOH)](/dotnet/standard/garbage-collection/large-object-heap). Because the LOH is not compacted, sometimes the LOH can be the source of fragmentation.
+
+## How to investigate a warning
+
+Click the **Investigate** link to go to the [Allocation](../profiling/dotnet-alloc-tool.md#allocation) view showing allocations grouped by heap type. Objects under the Large Object Heap node are contributing to the frequent GCs. Consider reducing these allocations through reuse or pooling techniques.

docs/profiling/perf-insights-loh-allocations.md

@@ -23,8 +23,8 @@ Frequent temporary LOH object allocations force unproductive full generation 2 (
 
 The [.NET Garbage Collector (GC)](/dotnet/standard/garbage-collection/) puts large objects in a specific region of memory known as the [large object heap (LOH)](/dotnet/standard/garbage-collection/large-object-heap). These allocations are assumed to survive longer due to their allocation cost and are therefore only collected during full [Gen2 GCs](/dotnet/standard/garbage-collection/fundamentals#generations).
 
-When this assumption is not true and an application frequently allocates temporary large objects, the LOH space is quickly used up. This causes many Gen2 GCs to regain space which can impact performance and responsiveness of an application.
+When this assumption isn't true, and an application frequently allocates temporary large objects, the LOH space is quickly used up. This causes many Gen2 GCs to regain space which can impact performance and responsiveness of an application.
 
 ## How to investigate a warning
 
-Clicking on the "investigate" link will take you to the [Allocation](../profiling/dotnet-alloc-tool.md?#allocation) view showing allocations grouped by heap type. Objects under the Large Object Heap node are contributing to the frequent GCs, consider reducing these allocations through reuse or pooling techniques.
+Click the **Investigate** link to go to the [Allocation](../profiling/dotnet-alloc-tool.md#allocation) view showing allocations grouped by heap type. Objects under the Large Object Heap node are contributing to the frequent GCs. Consider reducing these allocations through reuse or pooling techniques.

docs/profiling/toc.yml

@@ -58,6 +58,10 @@
         items:
         - name: LOH allocations
           href: perf-insights-loh-allocations.md
+        - name: Excessive induced GCs
+          href: perf-insights-excessive-induced-gcs.md
+        - name: High LOH fragmentation
+          href: perf-insights-high-loh-fragmentation.md
     - name: Analyze memory usage without the debugger
       href: memory-usage-without-debugging2.md
     - name: Custom native ETW heap events