Matthew Warren created two blog posts discussing the impact of garbage collection on application performance in .NET. In the first post, he discusses how ‘stop the world’ collections are inevitable, even in SustainedLowLatency mode, and publishes his test methods, tools and graphs. As part of the post, he mentions Azul’s pauseless garbage collector for Java and notes that he used some ideas from Azul CTO Gil Tene’s open source jHiccup tool in his testing.
In the second, he updates the post based on feedback he received from Mr. Tene and discusses the issue of coordinated omission in performance testing. The differences in the graphs when adjusted to compensate for coordinated omission are startling. Well worth a look if you are involved in performance testing applications.