If you ask me one tip to improve the performance of your applications, it would be:
Design your objects to be collected on gen #0 or not at all.
Naturally, following this recommendation demands you to know, at least the basics, of how the garbage collection works. But, if you are interested in improving the performance of your applications, this is necessary at all.
In fact, the garbage collector was explicitly designed to be very efficient performing gen #0.
Garbage collector gets more expensive in each generation. Even with background processing for gen #2, there is still a very high CPU cost to pay. Consider that you should avoid gen #1 collections too. In most scenarios, gen #1 objects are directly promoted to gen #2.
Ideally, every object you allocate goes out of scope by the time next gen #0 comes around. You can measure how long is that interval and compare it to the duration that data is alive in your application using tools such as PerfView (By the way, take some time and learn how to use PerfView – this is such great tool).
Time to action
Following this recommendation requires a shift in your mindset. It will inform nearly every aspect of your application (I strongly recommend you this Ayende’s talk about this topic).
Here are some guidelines to keep in mind when writing your code:
- Pool Long-lived and large objects – Consider following the same patterns adopted by the Roslyn team.
- Avoid copying data whenever you can. Use classes as ArraySegment and, now, the new Span<T> (Please, take some time and read this MSDN Magazine written by Stephen Toub).
- Reduce References between Objects – That would make the GC work less expensive. Also, it makes easier to predict object lifetimes.
- Be aware of the cost of finalizers.
- Use Weak References for Caching
Isn’t that enough? In the next weeks, I will share in-depth information about how you could follow these recommendations to get improved .NET applications performance. Sign in my contacts list, and you will receive notification when new content arrives.
Last but not least, remember that Performance is a feature. If the performance of your application is not that good, chances are you missing opportunities to deliver business value.
Cover image: chuttersnap
The post The #1 Rule for .NET Performance first appeared on ElemarJR.com.
Top comments (0)