top | item 25184405

(no title)

mish15 | 5 years ago

You just mmap memory as a slice. You can grow and shrink it, flush to disk if backed by a file, etc. In code it’s just a slice. Tough part is you need to allocate, control bounds, binary encode/decode, struct align, defrag, etc. It’s hard work, but the performance is 100% worth it if performance is your main goal.

discuss

order

chewxy|5 years ago

TIL mmap'd memory is invisible to Go's GC