Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Has someone used a configuration enabling the garbage collector optimized for multi-processor machines using Aspnet.config with :
<gcServer enabled="true"/>
<gcConcurrent enabled="true"/>
Was there an improvement in the performance of your site?
Are any problems noticed?
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.