@BeholdMiNuggets The README.md file is available in the repository. I've forgotten to include it in the binary releases, I corrected this for the v4.1.1.
About your example:
The GPU RAM buffer must be paired with a CPU RAM buffer. Also, another buffer needs to be created for each output file to store the staggerSize reordered plots.
As you want to plot in direct mode, the staggerSize doesn't have so much impact. It just needs to evenly divide the GRAM to free the graphic card in time to generate the nonces in parallel.
So let's say 8GB GRAM and 2x2GB RAM, for a total of 14GB RAM if you count the paired buffers.
8GB = 32768 plots
2GB = 8192 plots
7.9TB = 33046528 plots
The devices.txt file should contain:
<PLATFORM> <DEVICE> 32768 <LOCAL_WORK_SIZE> <HASHES_NUMBER>
With:
PLATFORM/DEVICE: The platform/device couple of your GTX1090Ti, as provided by the listPlatforms and listDevices commands, or by using the setup command.
LOCAL_WORK_SIZE: A GTX1080Ti posseses 3584 computing units. You can try 2048 for this parameter. If it is rejected by the card, divide by two, and so on (1024, 512, 256).
HASHES_NUMBER: 4096. If your screens blinks or you experience display driver crashes, use a small number, like 4.
The command line will be:
./gpuPlotGenerator generate direct <DRIVE1>:/<ADDRESS>_0_33046528_8192 <DRIVE2>:/<ADDRESS>_33046528_33046528_8192
With:
ADDRESS: The numerical value of your Burst address.
As discussed previously, depending on your disks, it may be better to plot on SSDs or to more disks at the same time to enhance the overall throughput.