Exactly, so I don’t need memory diagnostics running reserving space for office programs might I decide to start them or processes doing extra work compressing memory that’s needed again, thus decompressing again, adding extra steps for minimal to no gains in actual memory space.
From observation, once the sim starts falling behind you enter a downward spiral, more and more memory use trying to keep up, which causes more hard faults, which cause more slow down. The less interferes, the less chance the sim will fall behind.
This is nothing new, FSX had the same issues. It’s easily triggered when you accelerate time or use slew mode, or simply fly too fast too low. Somehow the sim can’t chuck out the old data fast enough and memory use keeps going up.
I had the whole thing balanced to work well with the Bonanza while hugging the terrain, then the Bonanza got a power boost and now flies 30% faster. Thus I needed my laptop to be 30% more efficient to keep up with the same settings. Hence reducing memory footprints and cpu usage of unnecessary background processes.
Successful so far, not a single CTD anymore since I turned off memory diagnostics and memory compression. A couple long pauses where it would previously have crashed, yet now it continues again after ‘taking a deep breath’.
Microsoft may have decades of experience with windows, so have I, been using windows since 3.1. I’ve worked with MSDev for decades, debugged lots of memory problems and have written my own memory managers. I have also flown over 1,200 hours in FS2020, 99% of it no more than a few thousand feet off the ground. Currently zooming along over Thailand, 175 knots GS, 6,000 ft (ground is at 4,000ft) 21.4 GB memory in use, 3 hard faults/sec, pagefile 19.7GB, all running smoothly.
Edit: I jinxed myself, it just crashed. No clue why, it was running smoothly and simply stopped mid flight.