Nordlandia wrote:Regarding 6-men. How much of an penalty is it to probe 6-men until RAM get full if paging file is on SSD?
I have plenty of space available on 850 EVO, so the question is if it's good idea to set paging file close to WDL size.
Windows will never page TB data from RAM to the paging file, since all TB data is already backed by the TB files. So if Windows decides to free up RAM currently used for caching TB data, it will simply release that memory. When it needs the same data again, it will reread it from the TB file.
So there is no reason to set the size of the paging file close to the size of the WDL tables.
The reason why things can get slow with heavy 6-piece probing is that Windows starts paging out your other programs. This can be prevented by disabling the page file. Without page file, Windows cannot page out the other programs and is forced to do what we want it to do: release the cached TB data.
It would be nice if there were a way to tell Windows that it should always prefer to release cached TB data over paging out active programs, but I am not aware of one.
What can help if SF + 6-piece TBs starts slowing down the PC is to set SyzygyPath to something non-existent and then change it back. This will unmap all mapped TB files. However, SyzygyPath cannot be changed while the engine is searching.
I might at some point add an option to Cfish to periodically unmap all mapped TB files.