Email or username:

Password:

Forgot your password?
Dr. Quadragon ❌

Found a nice writeup on avoiding triggering Go's Garbage Collector when storing a huge set of strings.

blog.gopheracademy.com/advent-

Kinda reminds me of Carmack's Megatexture approach, where all the textures on the map are baked into a large blob that is then fed into the GPU memory, and addressed by offset basically. Nice hack.

3 comments
:umu: :umu:
@drq basically having a pool in language that doesn't let you work with memory...
  Dr. Quadragon ❌

@a1ba To be fair, you'd only need this on very specific loads, like caches and such.

  Dr. Quadragon ❌

@a1ba Unless you're storing huge amounts of pointer-bound data at the same time, GC in Go is generally not a problem.

Go Up