3 ms·

Didn't Discord have issues when they did caching in Go due to the garbage collector having to run over all objects ever 2 minutes? Was that resolved in a newer

Didn't Discord have issues when they did caching in Go due to the garbage collector having to run over all objects ever 2 minutes? Was that resolved in a newer version of Go or does this project get around that problem in another way?

kissgyorgy 7y ago
Brad Fitzpatrick and others pointed out that in that article they were using Go 1.6, but the garbage collector got way better since then and it would be possible that just upgrading Go would have solved the issue for them.
hrgiger 7y ago
Seems like this has been merged: https://github.com/golang/go/issues/35112 https://github.com/golang/go/issues/35112 https://github.com/golang/proposal/blob/master/design/35112-scaling-the-page-allocator.md https://github.com/golang/proposal/blob/master/design/35112-...
- apta 7y ago
  As far as I know, without a generational or regional GC, golang will always have issues with large heaps.
mastabadtomm 7y ago
I don't know the Discord case but Olric implements an append-only log file indexed with a built-in map(uint64 > uint64) to store data.
- wlll 7y ago
  It was discussed here https://news.ycombinator.com/item?id=22238335 https://news.ycombinator.com/item?id=22238335
- marcinzm 7y ago
  Ah, as I understood it the Discord issues only shows up when you do a large long term map(? -> object) but maps with primitive values don't trigger it.