How does LINQ impact garbage collection generations in .NET runtime?

LINQ increases Gen0 allocations due to iterator objects and closures.

Each LINQ operation may allocate iterator objects, lambda closures, and intermediate enumerables. These are typically short-lived and collected in Gen0. However, high-frequency LINQ usage increases GC pressure, leading to more frequent collections and potential pauses. In extreme cases, Gen1/Gen2 promotions can also increase if objects are accidentally retained.