Games cap at 3gb ram (despite online benchmarks clearly showing they use up to 10)

1323114355

Commendable
Sep 21, 2016
42
0
1,530
Alright so I've ran into a problem for which I cant find a solution online, hope you can help. So I'm trying to play Deus ex: mankind divided however the game doesn't seem to even want to use more than 2.7 GB of ram. I've got 16gb in my Pc and i honestly cant find anything on this. I have windows 10 64 bit, so the possibility of it being caused by windows being 32 bit is ruled out. Thanks in advance :/
overall specs:
cpu: fx8350
gpu: gtx 1060
 
Solution
Windows keeps unused code around in ram in case it might be reused.
It does not necessarily mean that it is actively accessed.
One has to look at what the working set is.
One thing to check is your hard fault page rate,
A hard fault happens when the code accesses a page of virtual memory and gets a page exception because the page has been swapped out to the page file.

On a hard drive, this can be very painful, on a ssd much less so.
Look at your hard fault rate.
If it looks anything like one per second, then you certainly can use more ram.
Most games were developed in a 32 bit environment.
That had an arbitrary limit of 2gb for the user and 2gb for the system.
Later, there was code that let users increase that address space to 3gb.
I think that is what you have.
If a developer really needed more, they could do so, but would restrict their market.

If you are having performance issues, it likely is because of the poor single thread capability of the FX processor.
 

1323114355

Commendable
Sep 21, 2016
42
0
1,530


You're missing the point, benchmarks on youtube (same specs) show that its using 9 gb of ram and the game is not stuttering at all. On my pc, the same location in game, everything is the same including the settings, it stutters and it only uses 2.7gb.

benchmarks: 9gb ram used, 40-60 fps, no stuttering.
my pc: 2.7-3 gb ram used, <40 fps, constant stuttering.
 
Windows keeps unused code around in ram in case it might be reused.
It does not necessarily mean that it is actively accessed.
One has to look at what the working set is.
One thing to check is your hard fault page rate,
A hard fault happens when the code accesses a page of virtual memory and gets a page exception because the page has been swapped out to the page file.

On a hard drive, this can be very painful, on a ssd much less so.
Look at your hard fault rate.
If it looks anything like one per second, then you certainly can use more ram.
 
Solution