Skip to main content
The memory instrument captures detailed memory usage of your benchmarks, helping you identify and optimize allocations before shipping to production.

How does it work?

CodSpeed builds your benchmarks to run only once while measuring the memory. The profiling is done using a custom eBPF program ensuring stability and minimal overhead (depending on how allocation-heavy the benchmark is). The tracking is done by either instrumenting the dynamically loaded allocator libraries or your benchmark executable (when using a statically linked allocator). We track all allocation related functions (e.g. malloc, free, …) in your benchmark and spawned sub-processes.

What does it measure?