Likely caused of your stuttering was Witcher 3 writing to page file, instead of keeping everything in memory. If you have over 12GB of memory you should turn off your page file. Windows is needlessly writing to your drive while you have enough memory for everything. (some services like nvidia shadowplay is writing to your drive constantly recording your game footage - disabling it, will grant you considerable performance on hdd as well.)
8GB for hdd cache is a lot, not sure if you need it that much though. Still its very cool solution to your read speeds on hdd.
speed of hdd's are defined by following: - size filled (hdd's are considerably slower for newest data once you've filled more than 80% of your drive) - fragmentation (devil have mercy, because god won't) - partition (small sector size = poor write/read speeds and more space, large sector size = better write/reads and less space) - sata revision
Think your problem is located somewhere else then your HDs cache, atm im running witcher 3 off some cheap mechanical hard drive with no problems at all, can't even remember the maker of it. Albeit i turned off hairworks since i'm running a AMD GPU. Witcher doesn't require much loading on your hard drive, it loads most of what it uses by using trickery, and magic when moving across the map, or when the load screen is shown.
Agree but do so by making it small not off. Im not sure if it carried on to Windows 10 or not but if you disable the page file windows will make one anyway for kernel reasons it needs one I believe. Even if it's 512M it can't thrash.
Turning off paging file completely is not a good idea. Windows is designed to work with it. And some programs expect it to be there and they will simply refuse to run without it, regardless of how much RAM you have.
Ok, I misunderstood that. That being said, I recently moved W3 from my SSD to my HDD since I've finished the game. Aside from (in comparison) annoyingly long loading times, the overall performace seems to be the same.
i am aware of those claims, nevertheless if you have enough memory you can simply stop caring. It was implemented for times when there was not enough memory. They stated 'people have tested' and they don't point to any actual, factual tests.
In reality it does affect performance a lot on specific events.
by default windows will move un-used software paged pool to virtual memory page file. Lets say you haven't used firefox/chrome in 30min and you started playing a game, windows proceeds by moving it to page file - even if you have and had enough memory to keep it in memory.Once you close your game or minimize it, it will load it from page file. It will take considerable longer than if it was in memory.
There's much more to it, not only your application processes can use page file. As windows is designed to keep 3 types of page pools. (all of those page pools can be contained in memory only, but devices IRQL's might be mapped to your page file... and this is just a horror story for performance of that device - unless it doesn't require performance right now)
Thus it does affect burst performance; running actual benchmarks etc won't show anything being slower or faster - as windows will keep everything in memory.
Same goes to witcher, if some specific file thats open isn't being used for a while - whats the point of keeping it in memory? move to page file...