‹ 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. raverbashing · · focus · HN ↗
        Yes but then you can move your deallocation out of the critical path

        Variable time yes but you know when you're going to pay it

        (I mean yes you can put your gc.run() there as well, but it might not give you the results you want)

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.