Someone has used a configuration enabling the garbage collector optimized for multi-processor machines using Aspnet.config with :
gcServer enabled="true"
gcConcurrent enabled="true"
There was improvement in the performance of your site?
It was noticed a problem?
First, Concurrent and Server are mutually exclusive options. See this blog post for some details on server GC misconceptions. However, ASP.NET, by default, hosts the server GC (see Scott Hanselman's discussion), so there will be no difference there.
I'd recommend sticking with server instead of concurrent for an ASP.NET website. For a user-mode application, the concurrent GC has been user responsiveness, since the server gc will cause "hangs".
I have used the server GC, and noticed significant improvements in certain situations.
The server mode GC does help user apps, though, if you're user application is working with huge memory pools, and getting highly fragmented.
Simply put, the Workstation GC mode improves performance for a single user, while the server GC mode is designed for use on a program that has multiple requests all the time. I truly hope that this question isn't a symptom of a much larger problem. sometimes when people start questioning the garbage collector it's because they're not seeing memory footprint that they were expecting. don't expect great gains with a different garbage collector. In almost all the tests I've done, it's made little difference which collector you are using.