HN

Need help?
<- Back
Watching Go's new garbage collector move through the heap

Watching Go's new garbage collector move through the heap

matheusmoreira

Comments (16)

  • nomorewords
    This was very interesting, but the ending was a bit abrupt. I was under the impression that there was something more that I was missing under the subscribe banner.But to the point of the article - are there cases in which manually moving objects around to compact them in a specific area is done with golang? I don't use golang that much, and I'm sure that there are very strong arguments for not compacting the heap post-GC, but I've always wondered how it avoids crashing in the 0.0001% of cases in which heap is defragmented in such a way that there's no way to allocate a new large object
  • owaislone
    For anyone interested in this - https://www.youtube.com/watch?v=gPJkM95KpKo
  • okzgn
    Excellent optimization technique: manually copying objects to a new slice so they don't prevent the GC from releasing memory by sitting right in the middle of a page it intends to free.
  • KolmogorovComp
    Tangential but this makes me think of a video about C# GC, and the developer switching to Swift to avoid it, in which the dev says they estimate the development of a pause-less GC to be 5B$ R&D away, does that ring the bell to anyone?
  • extra-AI
    But if the objects being scanned are already located on the same page, aren’t we just wasting time managing the page and tracking the objects within it?
  • prathamdmehta
    that's very interesting with some blunt ending