Link Details

The original post was written in french, here is the google translation. The empirical analysis shows that an application in the vast majority of objects created are destroyed almost immediately. This is particularly true for web applications and / or stateless where most of the objects are created to deal with a complaint and therefore can be destroyed immediately after this treatment. From this follows the idea of not treat newly created objects and those who have been around longer. The Garbage Collector using implementations based on this principle are called generational GC. Can set two goals when optimizes GC: reduce breaks or increase throughput. These objectives are usually orthogonal (reducing the length of breaks comes at the cost of speed, and vice versa), they often depend on the type of applications in an interactive application, we are focusing on the breaks, and on the contrary, in a batch, only the debit account. The rest of the ticket is decomposed into two parts: * The first describes how generational traditional algorithms (Implementation current Sun JVM) * The second details of the new algorithm that Sun is trying to push for its future JVM