Does it mean the “depth map fusing” process consumed 833GB of data at its peak?
I’ve been monitoring its resource consumption and swap space usage only peaked at about 280megabytes, and hard disk consumption was about 450GB. My server has 512GB RAM so logically I would think the VmPeak & VmSize figures must represent a combination of RAM and hard disk…?
I did some searching about /proc/self/status which indicates VmSize refers to:
“the virtual size of the process” and
" VmSize also counts for memory mapped files (i.e. the executable file and all shared libraries it links to or other explicitly mapped files) and shared memory blocks" and
" VmSize accounts for all virtual memory allocations (file mappings, shared memory, heap memory, whatever memory) and grows almost every time new memory is being allocated. Almost, because if the new heap memory allocation is made in the place of a freed old allocation in the data segment, no new virtual memory would be allocated. It decreses whenever virtual allocations are being freed. VmPeak tracks the max value of VmSize - it could only increase in time".