Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@homo-lorens Not an idiot, it's common mistake.
Do you know what each value means :) -
@EpicofGilgamesh My concern was that 1.3G memory usage with no containers running, what I forgot was the fact that virtual memory isn't even proportional, let alone equivalent to, physical memory usage.
-
@homo-lorens
Simply put, virtual is anything that is referenced by the process. Shared Library between many processes is the easiest example. When e.g. the libc library is loaded, it's shared between many proceses. The process still references the memory, but - as it is shared - doesn't belong exclusively to the process.
Hence virtual. The definition of virtual changes every now and then, as Linux Kernel ABI is in flux.
Other examples would be mmap'ing a file. Part of the allocation is in resident memory, but it's largest part is virtual - as the file gets read from the HD.
Hardware memory used by the process is resident memory, e.g. what exclusively is used by the process.
Related Rants
Anybody got any idea WTF is going on?
rant
1.3gb
no containers
idle
docker
memory