Skip to main content
This is lesson 4 of 7 in this module Course 58% complete
Prev Next Skip

Generational Garbage Collection

Premium Content

Sign in with your account or sign up to access this lesson.

Sign In Sign Up

The lesson describes how mark-and-sweep causes pauses when all live objects must be re-scanned repeatedly, and how a three-generation garbage collector solves this problem by migrating surviving objects to progressively less-frequently-collected heaps. We illustrate the migration mechanics with concrete allocation scenarios.

Previous Next
Previous Module Array Performance Optimizations
This Module The .NET Garbage Collector
Introducing Garbage Collection (GC)
Introducing Garbage Collection (GC)
Mark and Sweep GC
Mark and Sweep GC
Heap Compaction and Object References
Heap Compaction and Object References
Generational Garbage Collection
Generational Garbage Collection
The Small and Large Object Heaps
The Small and Large Object Heaps
GC Performance and Assumptions
GC Performance and Assumptions
GC Memory Layout Strategies
GC Memory Layout Strategies
Next Module Memory Performance Optimizations