Knowing your garbage collector
Formal Metadata
| Title | Knowing your garbage collector |
|
| Title of Series | |
| Part Number | 27 |
| Number of Parts | 173 |
| Author | |
| License | CC Attribution - NonCommercial - ShareAlike 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Francisco Fernández Castaño - Knowing your garbage collector
As Python programmers we're used to program without taking care about allocating
memory for our objects and later on freeing them, Python garbage collector
takes care of this task automatically for us.
Garbage collection is one of the most challenging topics in computer science,
there are a lot of research around the topic and different ways to tackle
the problem.
Knowing how our language does this process give us a better understanding
of underlying interpreter and allow us to know why problems like cycles
can happen in CPython interpreters.
So, this talk aims to be and introduction to the topic and a walkaround
through different approaches followed in CPython and PyPy:
* Generational Reference counting with cycles detector on CPython.
* Incremental version of the MiniMark GC on PyPy. |
|
| Keywords | |