Go uses a concurrent garbage collector (GC), which means that it operates concurrently with the execution of Go programs and doesn't stop the world during its execution. This concurrent GC has been present in Go since version 1.5, released in 2015.
This is false. The Golang GC doesn’t stop the world during the entire mark and sweep, but it does briefly stop the world when the GC transitions between mark and sweep phases. It’s concurrent in the sense that application work can continue during the mark phase.
Wow. I was struggling to understand GC insights for a long time. Bill explains it very clearly in this talk. Thank you Bill!
@Wade Axton is it written in go?
thanks for clear explanation
Outstanding talk!
Go uses a concurrent garbage collector (GC), which means that it operates concurrently with the execution of Go programs and doesn't stop the world during its execution.
This concurrent GC has been present in Go since version 1.5, released in 2015.
This is false. The Golang GC doesn’t stop the world during the entire mark and sweep, but it does briefly stop the world when the GC transitions between mark and sweep phases. It’s concurrent in the sense that application work can continue during the mark phase.
Too boring
boriing is good in software engineering from what I hear
Nope