Raytrace Report - Virtual Memory values do not agree with Windows Task Manager

Synopsis

Solution

"....., you had inquired about the apparent disagreement between the TracePro Raytrace Report and the memory data reported in the Windows Task Manager. I performed a ray trace on a simple TracePro file and compared the TracePro Raytrace Report to the Windows Task Manager. Physical Memory - the "Free" value in TracePro agrees with "Available" in the Task Manager - the "Total" value in TracePro agrees with "Total" in the Task Manager - the "Used" value in TracePro does not correlate to any value in the Task Manager, but TracePro is simply reporting the difference between the "Total" and "Free" values above. Virtual Memory The Windows Task Manager includes data for "Commit Charge" and "Kernel Memory". These values do not correlate to the data displayed in the TracePro Raytrace Report. Page 6.27 of the TracePro 3.0 User's Manual indicates that TracePro is using data from the "GlobalStatusMemory" function of Windows, and further explains that the Virtual Memory data from this command is tied to the application instance, and therefore will not agree with data reported in the Windows Task Manager. I located the following reference to the "GlobalMemoryStatus" function on the Microsoft website: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecoreos5/html/wce50lrfGlobalMemoryStatus.asp"