.NET Garbage Collection Performance Sensitive Configuration Parameters

Garbage Collection is the integral part of .NET Framework.  The .Net garbage collector automatically allocates and releases the memory for your application.  The garbage collector engine performs a collection based upon the allocation being made reclaim the memory of objects that are no longer being used by application.  It is recommended to use default configuration value always but there might be cases when you might need to change it.  Following are two configuration parameters that can be tweaked for performance gains

Configuration
Open Source / Free Tools
<gcServer>
»        Specifies if the CLR runs server garbage collection
»        Server GC is optimized for throughput and multi-processor scalability
»        In the .NET framework 4 and earlier versions, concurrent garbage collection is not available when server garbage collection is enabled.  Starting with the .NET Framework 4.5, server garbage collection is concurrent and for using non-concurrent server garbage collection, <gcConcurrent> element can be set
<gcConcurrent>
»        Specifies whether the CLR runs garbage collection on a separate thread
»        Leave concurrent garbage collection enabled, if application involves heavy user interaction


Comments

Popular posts from this blog

Test Case Template for Project Using Agile Methodology

Measurement & Metrics

Performance Test Run Report Template