The garbage collector is that conscientious colleague who tidies up after everyone, right up until it decides to tidy up mid-request, at which point your p99 latency leaps and the entire team turns to look at you. Knowing what the GC is actually up to, and how to give it less to do, is the difference between software that scales and software that merely stutters apologetically. A deep, practical tour: how the generational GC really works, server versus workstation modes and the newer adaptive behaviour, and, the part you can act on first thing Monday: Span, Memory, stackalloc, ArrayPool and object pooling, with honest allocation measurement instead of optimistic guesswork.
You'll leave able to read an allocation profile, cut the garbage, and inform the GC, politely but firmly, that you've got this one.