In theory, everything is deallocated after the timing run.
However, real MemUsed (as reported by /proc/meminfo) remains high because memory allocator does not necessarily release all deallocated memory back to OS.
As a result, peak memory can be reached when reading SDP for the second time.
Below is an example. The spikes around 100s and before 400s represent reading (and synchronizing) SDP before timing run and actual run, respectively. Note that the spike is proportional to SDP size (16 GB in this case).
The orange curve shows current SDPB behavior. The blue one calls malloc_trim(0) after timing run and makes the peak lower.
In theory, everything is deallocated after the timing run.
However, real MemUsed (as reported by
/proc/meminfo) remains high because memory allocator does not necessarily release all deallocated memory back to OS.As a result, peak memory can be reached when reading SDP for the second time.
Below is an example. The spikes around 100s and before 400s represent reading (and synchronizing) SDP before timing run and actual run, respectively. Note that the spike is proportional to SDP size (16 GB in this case).
The orange curve shows current SDPB behavior. The blue one calls malloc_trim(0) after timing run and makes the peak lower.