= DWow, I have never seen anyone use such a large stagger size, interesting. Curious to see how it goes for you....Looking to get 100 drives plotted so any methods of speeding that up are great.
I like to go big *and* go home.
So far the large stagger size hasn't been as easy as I anticipated. At first, did nonces per plot = 4x stagger (even with stagger > 100GB. In direct mode, this caused quite an i/o performance bottleneck even on the NVME SSD.
Direct mode with stagger = nonces seems to work better. Sequential i/o still takes at least as long, if not longer, tban calculating the nonces, but I'm working on that.
I'm hoping that telling windows to run the "move" command in the background, after saving a plot file to the SSD, it should be able to start plotting the next file right away.
Logically, it goes something like this (syntax is very different):
batch file 1:
generate c:/plotfile1
async move c:/plotfile1 d:/plots/
generate c;/plotfile2
async move c:/plotfile2 e:/plots/
generate c:/plotfile3
move c:/plotfile3 f:/plots/
(repeat above with g:, h:/, i:/)
batch file 2:
generate c:/plotfile7
move c:/plotfile1 j:/plots/
generate c;/plotfile8
async move c:/plotfile2 k:/plots/
generate c:/plotfile9
async move c:/plotfile3 l:/plots/
(repeat above with m:, n:/, o:/)
So, on the first batch file, with any luck it will start the second plot immediately after the first, while the first one moves in the background. Same with the second plot file. The third plot file (and 6th, 9th, etc) will do a sync move to help make sure the SSD doesn't get full or bogged down.
On the second batch file, similar idea, except the first, fourth, seventh, etc plot will be moved syncronously, while the 2nd, 3rd, 5th, 6th, etc will move async. Hopefully this lets the nonce processing and the most intense portions of the ssd i/o be staggered a bit between the two batch files.
If it works as expected, I should be writing to up to 6 hard drives at one time.