VMware Cloud Community
mrstevejobs
Contributor
Contributor

Which is the real total consumed RAM?

I've been working with Siga and getting the RAM by using the ProcMem.getResident() method, which as detailed in the API docs:

Get the Total process resident memory.

Supported Platforms: All.

System equivalent commands:

  • AIX: top, ps
  • Darwin: top, ps
  • FreeBSD: top, ps
  • HPUX: top, ps
  • Linux: top, ps
  • Solaris: top, ps
  • Win32: taskman

Returns:
Total process resident memory

That function seems to return what in Windows Task Manager is called: "Working Set (Memory)".

But there are other measures in Windows such as:

  • Memory - Peak Working Set
  • Memory - Working Set Delta
  • Memory - Private Working Set
  • Memory - Commit Size
  • Memory - Paged Pool
  • Memory - Non-paged Pool

Which is the total memory of the process? According to Windows Docs it seems it is the Commit Size memory.

Also it might make more sense as the the "Memory - Commit Size"  looks always bigger than the "Memory - Working Set".

Is there a way of getting the Commit Size memory with sigar?

I'm monitoring some processes and I would like to know which is the real measure for the Memory. The total memory the process is consuming from the machine.

Thanks a lot!


Reply
0 Kudos
1 Reply
Ethan44
Enthusiast
Enthusiast

Hi

Welcome to communities.

the working set is a count of physical memory (RAM) rather than virtual address space.

It represents the subset of the process's virtual address space that is valid,

meaning that it can be referenced without incurring a page fault.

The commit size is:

the total amount of pageable virtual address space for which no backing store is assigned

other than the pagefile. On systems with a pagefile, it may be thought of as the maximum potential

pagefile usage. On systems with no pagefile, it is still counted,

but all such virtual address space must remain in physical memory (RAM) at all times.

Reply
0 Kudos