Well, as mentioned in the Hollo Pointe thread I was going to do a test with PG and the F-14 to see what happens with RAM usage. I have 32GB of RAM on my system.
To start with, we have to acknowledge that what the task manager indicates in Windows 10 does not represent the total usage of RAM for a process. This represents the “Private” memory if some quick math (while the numbers change constantly on my screen) matches up.
The resource monitor is our friend in this case, as we want the “Working Set” which is measure in KB.
(Remember 1MB = 1024KB)
The Working Set is defined as: “Amount of PHYSICAL MEMORY currently in use by the process”.
The numbers below are working set, converted from KB -> MB -> GB and are solely for the DCS process. RAM in use by other processes can be seen partially in the images.
For the purpose of this test we are using the following graphics options:
The missions is “Divine Falcon” on Hollo Pointe North, about 2 hours in. Cue the numbers!
Stage 1: Loading to the Slot Selection Screen
We are already at 12,525,676KB / 12,232.11MB / 11.95GB
We already have hard faults, meaning Window’s is working with the page file.
Stage 2: F-14 selected and loaded in.
Now: 14,824,364KB / 14,476.92MB / 14.14GB
Stage 3: Cycling F2 Camera Around
Now: 17,858,936KB / 17,440.37MB / 17.03GB
Hard faults are ramping up significantly as we use up RAM.
Stage 4: Cycling F11 Camera around the Map
Note - this stage and on would be “abuse”, just trying to push it to see how far it will go.
Now: 25,192,552KB / 24,606.00MB / 24.03GB
Hard faults continue to grow massively.
Stage 5: Maxing Out
Here we hit the peak. Task manager is indicating low RAM and it appears we got things mainly in physical memory as hard faults have dropped down again.
Now: 26,515,724KB / 25,894.26MB / 25.29GB
I’m thinking I should have bought 64GB instead…but to be fair, F11 flying around the entire map is not what we would call typical usage.