You can avoid internal benchmarking on restart by specifying the result explicitly like this:
path=F:\farmer1,size=500GiB,record-chunks-mode=ConcurrentChunks
Then restart is much faster.
Can you be more specific? Piece cache sync (assuming it finished successfully last time and you had large enough total space) will finish after all piece cache is read, which also doesn’t take a long time.
And I don’t expect you need to resart often anyway, one minute when you restart doesn’t really change anything.
If my assumptions are not correct then there is a potential to improve performance.
This makes no sense because you will trigger piece cache sync from scratch and eventually will not have all the pieces cached locally, which basically means you are losing more time and bandwidth on plotting overall than saving on restart.
Are you really having 48G of RAM used by jun-11 release with just 3*500G farms? That is very bad. If so how much time does it take you to reproduce this?
User in High RAM usage for May 15th release had tens of farms and WAY bigger Epyc CPU and I don’t think they had this high memory usage after fixes that went into jun-11. Can you double-check that you definitely use jun-11 release? I strongly prefer when people don’t rename it into farmer.exe to prevent potential confusion. You already had farmer1, farmer2 and farmer on screenshots.