Hyperion Entertainment Message Boards

My program does a lot of on-the-fly memory allocations: small amounts of memory (< 128 bytes) constantly get allocated and freed. I was wondering if using a memory pool would be more considerate of the memory system, especially as regards fragmentation.

Yes.
It also provides a simple way to free the entire pool if desired.

If your "small amounts of memory" are all the same size, you might also consider an ItemPool (ASOT_ITEMPOOL) instead of MemoryPool(ASOT_MEMPOOL), which can optimize for many same-sized allocations.

trixie wrote:My program does a lot of on-the-fly memory allocations: small amounts of memory (< 128 bytes) constantly get allocated and freed. I was wondering if using a memory pool would be more considerate of the memory system, especially as regards fragmentation.

Are these items all of the same size? If so, please use item pools instead. They're designed especially for the frequent allocation and deallocation of small blocks that are all the same size.

Look up ASOT_ITEMPOOL, ItemPoolAlloc()/ItemPoolFree() in the Exec autodocs.

Hans

Thank you both!