• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dumb top question...

Armitage

Banned
Watching the top output, my program shows 142MB virt and 105MB res. This is on a machine with 2GB RAM

I assume this means Virtual (swapped to disk) and Resident (RAM). Correct?

So ... I could potentially run this on a machine with only 256MB, since only 105MB is actually in RAM?

Anybody understand how this memory management works? I'm curious why a program that I just started, that has the CPU pegged on an otherwise idle machine would have over half the memory swapped out.


 
VIRT -- Virtual Image (kb)
The total amount of virtual memory used by the task. It includes all code, data and
shared libraries plus pages that have been swapped out.

VIRT = SWAP + RES.

q: RES -- Resident size (kb)
The non-swapped physical memory a task has used.

RES = CODE + DATA.
 
Back
Top