Server GC is a tradeoff between latency and throughput. It makes a ton of sense for a web server where a small additional overhead of a few milliseconds on some responses won't matter.
Workstation GC is what you want when latency is critical. This is what you'd use if you were developing a UI or game engine.
I've seen workstation GC stay in the microsecond region when strategically executing GC.Collect at allocation batch boundaries.
ozim
Well great but you did not write out anything more than I could understand as a 15+ years developer of C#/.Net from whatever all those people in Stack Overflow wrote.
Do you have anything like running a business line application for couple of years on Server GC to write about?
Workstation GC is what you want when latency is critical. This is what you'd use if you were developing a UI or game engine.
I've seen workstation GC stay in the microsecond region when strategically executing GC.Collect at allocation batch boundaries.