Max Load on pagefile causes FPS drop.

So, with 16gb of ram, 20000mb of pagefile on SSD, I get an fps drop to some 10fps after pagefile reaches full load. It happened already 2 times in the last 5 days on two different server, with not more than 20 ground units and a couple of planes. I know its the pagefile that causes this fps drop, because I do monitor the pagefile usage. There are no problems with game performance until pagefile reaches its limit.

3GB of VRAM + 16GB of RAM + 20000mb of pagefile. Anyone had similar issue?

Hate to be the bearer of bad news but...I think you would see a big improvement if your video card had MINIMUM 6GB.

If you are hitting your swap file, you are maxing out the onboard video memory...then maxing out the onboard system (RAM) memory and then your SSD is suffering.

Which OS do you use?? you are aware with Win 10 v 1703 and up have issues with Standby memory loading up and not working right to clear the Standby memory??

Also on your Graphics setting turn Terrain Textures to low, you will not notice a difference but High uses more v Ram ;)

You should be good on that system at lower settings. but you seem to be doing that..

I would also go with a bigger pagefile, I get to 20000 offline, I just let windows look after it. Try 25000 and see how it goes.

make it 32GB fixed size and call it a day :)

Mine is seldom below 20-21GB

Windows 10, yes. I have increased the size to 25000MB.

Windows 10, yes. I have increased the size to 25000MB.

better ??

So, with 16gb of ram, 20000mb of pagefile on SSD, I get an fps drop to some 10fps after pagefile reaches full load. It happened already 2 times in the last 5 days on two different server, with not more than 20 ground units and a couple of planes. I know its the pagefile that causes this fps drop, because I do monitor the pagefile usage. There are no problems with game performance until pagefile reaches its limit.

 

3GB of VRAM + 16GB of RAM + 20000mb of pagefile. Anyone had similar issue?

No, as you should let Windows 10 manage the Pagefile dynamically, not set it yourself.

The root cause is the 3GB VRAM as this is far below the recommended 8GB VRAM or better(!) specs.

You can only try to set everything to low and omit populated areas on the maps.

better ??

With terrain textures on low, yes.

No, as you should let Windows 10 manage the Pagefile dynamically, not set it yourself.

 

The root cause is the 3GB VRAM as this is far below the recommended 8GB VRAM or better(!) specs.

You can only try to set everything to low and omit populated areas on the maps.

But what was the thing with new and old ram usage management?

No, as you should let Windows 10 manage the Pagefile dynamically, not set it yourself.

 

The root cause is the 3GB VRAM as this is far below the recommended 8GB VRAM or better(!) specs.

You can only try to set everything to low and omit populated areas on the maps.

Dynamic is ok too, it should let you have enough PageFile. the downside of that is that your OS needs to "think" about what it does, enlarge or make it smaller..or leave it at the size it currently is.

With setting a fixed upper and lower limit which are equal you take that part out of the game. Tell it it's size and to shut up and just do it's job ;)

This is how I understood all the pages I read over the years from 95 to 10 about PageFile. many things changed but that rule still seems to hold true.

It's less overhead, less work, but confidence.

Dynamic is ok too, it should let you have enough PageFile. the downside of that is that your OS needs to "think" about what it does, enlarge or make it smaller..or leave it at the size it currently is.

 

 

With setting a fixed upper and lower limit which are equal you take that part out of the game. Tell it it's size and to shut up and just do it's job ;)

 

 

This is how I understood all the pages I read over the years from 95 to 10 about PageFile. many things changed but that rule still seems to hold true.

It's less overhead, less work, but confidence.

As Windows also puts certain backup and config data into the pagefile in case of a recovery after a crash, defining the size manually is a delicate job. Have you considered all background services? How much restore data for dynamic USB drivers/cache etc., config info for programs and what not could be required? How small can the pagefile be at start, without the OS immediately need to grow it to a working size? Where is the limit for maximum size when all processes run and is it effective to allocate the blocks/pages on the HDD/SSD and is the read schema (at least for the HDD) optimized?

You can try it of course, and if it yields better result, why not. But if the results don't change, I would revert to the OS controlled pagefile.