Developer knowledge network · moderated exchange

Супольнасць UnreliableCode

Супольнасць распрацоўшчыкаў даследаванняў, зваротнага праектавання і кадавання

Knowledge indexжыць
4Categories
919Threads
2.8KПаведамленні
Discussion

How to avoid memory fragmentation in high-performance C++ using custom Arena and Pool Allocators [StackOverflow Architecture Guide]

profiler_pat
Performance Hunter
MEMBER
прадстаўнік: 146
Дата далучэння: Aug 2019
Паведамленні: 33
Дзякуй: 31
3 тыдняў таму · Jul 29, 2026 2:24 AM
#1

Why general-purpose malloc / new causes memory fragmentation in long-running services:

General allocators add metadata headers (8-16 bytes) to every allocation and search free lists, causing heap fragmentation over millions of allocations.

Arena (Bump) Allocator:

  • Pre-allocates a contiguous 10MB memory block.
  • Allocating is a simple pointer increment (pCurrent += size). Sub-nanosecond execution time!
  • Freeing everything resets the pointer back to start in 1 CPU cycle (pCurrent = pBase).
memory_model_mook
Low-Level C Veteran
MEMBER
прадстаўнік: 163
Дата далучэння: Jan 2019
Паведамленні: 11
Дзякуй: 33
3 тыдняў таму · Jul 29, 2026 8:30 AM
#2

Arena allocators are standard in web servers and game engines for per-frame or per-request scratch memory.

raii_clean_coder
Modern C++ Advocate
MEMBER
прадстаўнік: 190
Дата далучэння: Aug 2020
Паведамленні: 20
Дзякуй: 22
3 тыдняў таму · Jul 29, 2026 9:43 PM
#3

Zero fragmentation, zero free-list traversal, and 100% cache locality.