Trying to make sense of the new memory(?) stats in 0.7.4

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
hanker
Newbie
Newbie
Posts: 27
Joined: December 8th, 2011, 9:25 am

Trying to make sense of the new memory(?) stats in 0.7.4

Post by hanker »

Greetings

I have just upgraded to 0.7.4 on a Debian squeeze system. This is running on a Seagate Dockstar, which has 128 MB of RAM and 999 MB of swap. Currently the output of htop is

Code: Select all

  CPU[||               3.9%]     Tasks: 70 total, 1 running
  Mem[|||||||||||||49/122MB]     Load average: 0.17 0.38 0.26 
  Swp[|             3/999MB]     Uptime: 11 days, 18:42:22
So 49 of 122 MB memory used and 3 of 999 MB swap used, where

122 = 128 * 1e6 / (1024 * 1024)

sab says this:

Code: Select all

Sysload: 0.16 | 0.41 | 0.27 | V=272M R=18M
What do those "V" and "R" numbers mean? Where do they come from?

User avatar
sander
Release Testers
Release Testers
Posts: 6986
Joined: January 22nd, 2008, 2:22 pm

Re: Trying to make sense of the new memory(?) stats in 0.7.4

Post by sander »

You were participating in the thread were this was born. See http://forums.sabnzbd.org/viewtopic.php ... 777#p71152

V = VIRTual
R = RES

See "man top" for the exact meaning of these numbers.

EDIT:
VIRT stands for the virtual size of a process, which is the sum of memory it is actually using, memory it has mapped into itself (for instance the video card’s RAM for the X server), files on disk that have been mapped into it (most notably shared libraries), and memory shared with other processes. VIRT represents how much memory the program is able to access at the present moment.

RES stands for the resident size, which is an accurate representation of how much actual physical memory a process is consuming. (This also corresponds directly to the %MEM column.) This will virtually always be less than the VIRT size, since most programs depend on the C library.

hanker
Newbie
Newbie
Posts: 27
Joined: December 8th, 2011, 9:25 am

Re: Trying to make sense of the new memory(?) stats in 0.7.4

Post by hanker »

sander wrote:You were participating in the thread were this was born. See http://forums.sabnzbd.org/viewtopic.php ... 777#p71152

V = VIRTual
R = RES

See "man top" for the exact meaning of these numbers.

Yes, I remember :)

I'm just used to looking at htop's overall stats, which are a different thing I guess. It sort of confused me how VIRT could be greater than the total amount of memory the machine has plus the total amount of swap in use. But yes, it does match the output of top.

Thank you for your reply. sab and sickbeard still working perfectly.

Post Reply