3 ms·
Here is what Ian lance Taylor has to say about fragmentation[1] "Heap fragmentation is not normally a concern with the current Go runtime. The heap is impleme
by geodel 10y ago
Here is what Ian lance Taylor has to say about fragmentation[1]
"Heap fragmentation is not normally a concern with the current Go runtime. The heap is implemented to that large pages are divided up into blocks that are all the same size. This means that the usual definition of fragmentation--a small block prevents coalescing of large blocks--can not occur. "
1. https://groups.google.com/d/msg/golang-nuts/Ahk-HunIqgs/1sOi8t5iCQAJ https://groups.google.com/d/msg/golang-nuts/Ahk-HunIqgs/1sOi...
- vvanders 10y agoThat's not any different than most C malloc implementations, it certainly helps with fragmentation but doesn't eliminate it as a concern. You can still have a single allocation in a block that'll hold the whole block hostage. I'm used to systems that vary from 8-512mb of total system ram with no virtual memory. Techniques that work well on the desktop/server explode spectacularly when brought to our platforms.