‹ BackHN Continuity

Thread

A 40ms Go garbage collector pause caused by swap

92 points · 85 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. groestl · · focus · HN ↗
      Overhead per allocation, if you care about that, and reference circles.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.