High LOH Fragmentation
This article describes performance insights for high large object heap (LOH) allocations.
The large object heap (LOH) 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.
The .NET Garbage Collector (GC) puts large objects in a specific region of memory known as the large object heap (LOH). Because the LOH is not compacted, sometimes the LOH can be the source of fragmentation.
Click the Investigate link to go to the 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.