Meaning of SystemInfo Memory Variables

[steveh01]

What do these refer to? :

SystemInfo.ProcessMaxVirtualSize,    SystemInfo.ProcessVirtualSize,    SystemInfo.PhysicalMemoryTotal,    etc.

Do they refer to the amounts of memory used by DIAdem? Are the virtual sizes supposed to be the same as shown the Windows 10 setting: “Adjust the appearance and performance of windows” > Advanced > Virtual Memory > Change? What are the units? KB (which is really KiB)? This website (http://www.savvydiademsolutions.com/script.php?topic=Checking-virtual-memory-size-in DIAdem-2015-and...) seems to indicate that the values are in KB (really KiB). However, I cannot confirm that, because I cannot get anything to match up.

[Salazar.Slytherin]

I matched up the available physical memory reported from DIAdem (863420) with the available physical memory shown in the Windows Task Manager (~830 MB). From that comparison, I'd say that DIAdem is reporting in KB

[steveh01]

I was hoping for a bit more than that.  I have been able to get one theory to line up with one number, but then when I look at the others and it does not agree, I go back to the drawing board.  I would also hope for a closer correlation.  I would expect 863,420 KiB reported by DIAdem to become 863,420 / 2^10 = 843 MiB (which is reported as "MB" by Windows).  830 MB is close, but still doesn't give me that warm fuzzy feeling of knowing  for sure that DIAdem is really reporting those numbers in KB.

Is there anything more authoritative, like someone who has consistent correlation for multiple numbers, or a developer who just knows what they are and what they measure?

[Walter_Rick]

Hi steveh01,

SystemInfo.ProcessMaxVirtualSize and SystemInfo.ProcessVirtualSize are of interest for 32-bit applications. For 64-bit applications these info’s are (more or less) not of interest because you have memory enough.

The info’s about memory in W10 which you see in the Task Manager is a bit confusing. These info’s doesn’t match with info’s from other tools. For example, if you use the “Process Explorer” from “Sysinternals” you will see that these info’s match with DIAdem but not with the Task Manager. Do you know this example from the DIAdem help?

Dim sOutput

sOutput =           "No. of CPUs:                   " & VBTab & CStr(SystemInfo.CPUCount) & VBCrLf

sOutput = sOutput & "Total physical memory:         " & VBTab & CStr(SystemInfo.PhysicalMemoryTotal) & VBCrLf

sOutput = sOutput & "Available physical memory:     " & VBTab & CStr(SystemInfo.PhysicalMemoryAvailable) & VBCrLf &VBCrLf

sOutput = sOutput & "Total commit size:             " & VBTab & CStr(SystemInfo.SystemCommitLimit) & VBCrLf

sOutput = sOutput & "Total used commit size:        " & VBTab & CStr(SystemInfo.SystemCommitTotal) & VBCrLf

sOutput = sOutput & "Process information:           " & VBCrLf

sOutput = sOutput & "Used physical memory:          " & VBTab & CStr(SystemInfo.ProcessMemoryUsage) & VBCrLf

sOutput = sOutput & "Maximum virtual size:          " & VBTab & CStr(SystemInfo.ProcessMaxVirtualSize) & VBCrLf

sOutput = sOutput & "Virtual size:                  " & VBTab & CStr(SystemInfo.ProcessVirtualSize) & VBCrLf

sOutput = sOutput & "Commit size used by process    " & VBTab & CStr(SystemInfo.ProcessCommitSize) & VBCrLf

sOutput = sOutput & "No. of GDI objects:            " & VBTab & CStr(SystemInfo.ProcessGDIObjects) & VBCrLf

sOutput = sOutput & "No. of handles:                " & VBTab & CStr(SystemInfo.ProcessHandleCount) & VBCrLf

Call Msgbox(sOutput)

Greetings

Walter

[steveh01]

Interesting. ... A bit more info. than before.  So, there may be a difference between what the variables mean for 32-bit and 64-bit operating systems, and the variables' original intended environment was a 32-bit operating system (although, I don't understand why you automatically have memory enough in a 64-bit system).  ...  The values for the variables don't necessarily match with what is shown in Task Manager for MS Windows 10.

Yes, the example from DIAdem help you are showing is the one that sparked all these questions.  I guess my deeper question is, how do we use these values programmatically?  Why do we need to know them?  (If there are meaningful answers to these questions in a 32-bit system, then I wouldn't think the purpose would just go away in a 64-bit system.)  Particularly, I am looking to increase DIAdem's data acquisition throughput ability during single-point processing and/or packet processing, and I'm wondering if any of these could be a key to doing that.

Thanks,

Steve H

[steveh01]

I am using a 64-bit MS Windows 10 operating system.

[Walter_Rick]

If you run a 32-bit application, this application can manage only 2 G byte of memory. A 64-bit application doesn’t have this restriction. That’s the big different. Yes, as I already mentioned the values of the DIAdem variables typically don’t match with the info of the Task Manager. But they match with for example “Process Explorer” from “SysInternals” (https://docs.microsoft.com/en-us/sysinternals/) which is from Microsoft. To getting to know what exactly is shown in the Task Manager, I think you must ask – or look – in Microsoft forums.

The system info values of DIAdem are not necessary to configure, create or run a DIAdem job. These values are only used for information. For example, if you have two PC running the same DIAdem application (scripts) and one PC is faster than the other one, it can help to find the reason.

In your case these info’s will not help. For this it is more a question of what are you doing and how? For example, if you are measuring data in the single processing mode you can do that in software clock and hardware clock mode. One has a limited clock rate and is very flexible and the other one is very fast. The packet processing mode is more used for online mathematic like FFT or similar things.

Greetings

Walter