Windows 10 Memory Compression negatively impacts developer productivity on "large" memory systems #35
Thanks for opening this issue. As the person who reported it on twitter I appreciate having this issue formally recorded.
I can see two possible ways of improving this situation:
On my testing i found a 7,3% performance penalty when running blender from compressed memory, (24,5gb vs 7gb).
My main use case continues to be using VsChromium. I'll have 30+ GB of available memory, then Windows will decide to compress VsChromium's memory, which means that my next search will take several seconds instead of being instantaneous. A few second delay isn't the end of the world, but it defeats the entire purpose of VsChromium which is to have all of Chrome's source code loaded into RAM and ready for instant access. Not access with a few seconds of delay, but instant.
Indeed. Would be very useful if microsoft allowed the user to customize MMAgent behaviour, especially on systems with lot's of memory. It's a shame that such an useful feature is causing problems for being overly agressive