Garbage collection is a way of automatic memory management provided by modern programming languages like Java, Go, Python and JavaScript.

We talk about how garbage is identified, the tricolor algorithm, the generational hypothesis and it's effect on latency and throughput.

Scenarios where the generational hypothesis doesn't work are also discussed. This includes caching and nepotism in queues (old generation objects promote young ones without due cause).

0:00 - Agenda
0:38 - Garbage Identification
0:50 - The Tricolor Algorithm
2:53 - Making the GC run faster
3:12 - Concurrent Collectors
3:49 - Generational Hypothesis
4:50 - Memory diagram
7:43 - Code injection JIT
9:09 - General hypothesis exceptions
9:43 - Nepotism

Part II: [ Ссылка ]

References:
Tricolor Algorithm: Knuth, The art of computer programming
Generational Hypothesis: [ Ссылка ]

System Design Video Course: [ Ссылка ]

Software Engineering Fundamentals: [ Ссылка ]

You can follow me on:
Instagram: [ Ссылка ]
LinkedIn: [ Ссылка ]
Quora: [ Ссылка ]
Twitter: [ Ссылка ]_

#GarbageCollection #JavaGC #JavaGarbageCollection

свернуть