-
Alexis SALZMAN authored
xDeltaMemory class is built in the same spirit as xDeltaTime. A "start" method capture a state and a "end" method do a comparison with previous captured state. This comparison give a measure of memory consumption between those two events. To be as precise as possible the usual string used to flag measure are now forcedly used by initAccu method and user must use startAccu, endAccu with the integer returned by initAccu. It give result like xDeltaTime as table with parallel statistic and Peak memory usage. This last information comes from getrusage (like xMemoryMonitor) and correspond to maximum resident set size. All other information are related to user request and do not represent the application true current memory consumption: malloc may have already reserve 2GB and user vector may use only 1.5GB. This is this last information that is given by xDeltaMemory. Only Heap is analyzed. Behind the curtain: =================== xDeltaMemory used deprecated GNU...
0628714a