mmm

Wouldn’t the GC be able to just stop scanning memory once it encounters an off GC heap pointer (since it knows what address ranges it manages)? I’ve only allocated non-pointer-containing Go objects manually (that presumably wouldn’t be scanned anyway) and it’s hard to find the specifics of how things work, although it seems like there are some libraries that allow it. [1] Since it’s possible to use C data structures and pointers directly from Go that seems like the safest way to do it, although of course then you need a C toolchain installed. [1] https://github.com/teh-cmc/mmm

You could manually manage memory in Go if you want. Here's a few links: https://news.ycombinator.com/item?id=9545873 https://github.com/teh-cmc/mmm

Thank you for making the comment I wanted to make, but was too afraid of being down-voted for being an elitist UNIX beard. Also funny that they admit the CPU use might not really be a problem... but try to solve it anyway and add a lot of complexity to their system. I have learned to KISS and am I am surprised they are solving this problem and don't have more pressing product development. Doing something like this is pretty standard, but doing it before its needed smells of misused engineering time. Also they didn't even really need to do most of the work they did here, they could have re-used existing out-of-heap Go memory mgmt solutions like: https://github.com/teh-cmc/mmm . But I get it, building things is fun :) But like the parent said, I'd expect it to be a personal rather than a company project.