‹ BackHN Continuity

Thread

A 40ms Go garbage collector pause caused by swap

94 points · 92 comments · shellpipe

  1. raverbashing · · focus · HN ↗
    I don't get why people do not prefer reference counting, it has more predictable runtime performance

    (though of course a swap is a swap - but you can "trigger" it depending on your memory or file access pattern)

    1. bheadmaster · · focus · HN ↗
      > more predictable runtime performance

      Not really, reference counting can cause a single object deallocation to trigger an arbitrarily long chain of deallocations.

      1. Findecanor · · focus · HN ↗
        Immediate reclamation, yes. There do exist a number of reference-allocation algorithms that performs deferred reclamation similar to how tracing GC does.
        1. amelius · · focus · HN ↗
          Yes, but that still leaves the circular dependency problem.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.