|
|
|
|
|
|
by DustinGadal
1132 days ago
|
|
|
On platforms that allow overcommitment, you can guarantee your commit charge is physically backed by writing to each page in a memory pool at allocation time (probably at application startup, or at the end of the main loop), then allocating out of that pool. Using memory that's been allocated but not committed seems like a recipe for disaster. |
|
|
It can greatly accelerate sparse datastructures.