Garbage Collection is one of the most important and vital aspects of compiler design that has a direct impact on the performance and speed of execution for a program. The .NET Framework has a very powerful and sophisticated garbage collector in its virtual machine that is not discovered very well, and it didn’t have any major changes since the initial release of version 1.0 of the framework until the most recent version, 4.0, where Background Collector was added to improve the quality of garbage collection. In this article the principles of garbage collection are reviewed, fundamentals of garbage collection in .NET are discovered, and the changes to garbage collector in .NET Framework 4.0 are discussed.
Starting a Ph.D. program in Computer Science by primarily specializing in the field of Programming Languages and Compilers, I learned a lot about compiler construction and the principles associated with it. One of things that I noticed in the past 1.5 years of this program was that many software developers who even work at a professional level and apply a compiler, don’t have a very solid understanding of the features of the compiler that they’re using everyday, and this weakness is more severe on the .NET community where the use of development tools and IDEs has automated a big portion of the process that is going on behind the scenes. Although it’s not reasonable to expect everyone to be a compiler expert, it’s very important to know some principles about the compiler that you’re using because such a knowledge can help you build programs with a higher performance and less resource usage.
Read more: Keyvan Nayyeri
QR:
Posts
