Improvise Garbage Collector performances
Generations: Improving Performance Thanks Jeffrey, The CLR’s GC is a generational garbage collector (also known as an ephemeral garbage collector , although I don’t use the latter term in this book). A generational GC makes the following assumptions about your code: The newer an object is, the shorter its lifetime will be. The older an object is, the longer its lifetime will be. Collecting a portion of the heap is faster than collecting the whole heap. Numerous studies have demonstrated the validity of these assumptions for a very large set of existing applications, and these assumptions have influenced how the garbage collector is implemented. In this section, I’ll describe how generations work. When initialized, the managed heap contains no objects. Objects added to the heap are said to be in generation 0. Stated simply, objects in generation 0 are newly constructed objects that the garbage collector has never examined. Figure 2...