|
OK Guys, no flames please, but what you need to check in Windows Task Manager is the Virtual Memory {VM} size, *not* the entry for "Mem Usage". {I think it is also sometimes called virtual machine size}.
As has been explained to me, the VM Size is the actual memory use of the process, not the "Mem Usage" entry. The "Mem Usage" entry reflects the address space currently allocated to the process which can be used without causing a page fault. Some of that address space can be reassigned to other processes if needed, but the VM Size is private to the process and cannot be reassigned.
My PC {WinXP-SP2, Pentium-4 2.4GHz CPU, 1-Gig RAM} has been running over a day now without reboot, with the Microsoft A.S. Beta running resident, so the following numbers for VM Size should reflect an "equilibrium" or "steady-state" typical RAM usage.
As I mentioned in previous post, the resident processes loaded by this program {identical to the processes loaded by its predecessor GIANT A.S.} are:
1. gcasServ.exe {Microsoft AntiSpyware Service} VM Size: 2372K 1. gcasDtServ.exe {Microsoft AntiSpyware Data Service} VM Size: 5908K
To get the VM Size to display in your Windows XP Task Manager: View, Select Columns -- check VM Size.
As you see, my box is showing a Grand Total VM Size of 2372K + 5908K = 8280K, or about 8 Megs. For anyone with enough RAM to run Windows XP, that isn't much. The GIANT A.S. on my son's 98SE PC, a box which has only 128 Megs total RAM, does not make much a dent there either. And the CPU overhead due to GIANT running resident on his PC, measured by Norton System Doctor, is almost a flat-ZERO. I'm talking about a very slow Cyrix 176MHz CPU, too.
I think the resource usage is a "red herring" or moot issue here. If you don't have spare resources to run this program, you don't have resources to run much of anything else either, IMHO.
Have a nice rest of the Saturday, everybody!
Attachment
#1, (gif file)
|