GoKawiilDeep dive explains how glibc's malloc minimizes brk syscalls
A technical write-up traces how glibc's malloc implementation manages memory requests internally rather than calling the kernel every time. Using strace on a test program that calls malloc(16) a thousand times, the analysis shows only two brk syscalls occur in total: one to check the current program break and one to extend the heap by 132 KiB, with the remaining 999 allocations served from that pre-reserved memory.