Hello forum, apologies for the barrage but I have a few questions regarding multi plot files and multi hdd mining.
1. Multiple FilesOk so I have my first hdd plotting and mining away without issue (touches all the wood, no homo)
If this my first plot file:
generate
0 10000000 8191 6
and supposing that it ends dead on 10E6
,will I start the following file as:
generate 10000000 10000000 8191 6
,or:
generate 10000001 10000000 8191 6
1.1.
Will the miner continue to the next file by itself or must I restart and where would it restart from should I restart the miner at anytime anyway?
2. Multiple HDDs
When I start plotting on a new hdd, do I start the plot from 0 again.
i.e. generate 0 10000000 8191 6
,or do I begin from where this first hdd will finish?
Since I read a post a couple of pages back that would suggest the latter, does that mean that the start point is arbitrary and what does that mean for a plot section that has already been mined?
3. From http://burstcoin.info/faq.php
This is question 4 (and 9) on the FAQ and seems to be contradicted by question 16, which states that the best method is by using a mining instance for each drive.
Can I have multiple files in my plots folder?
Yes, you can even create symlinks to other drives, letting you mine with just 1 instance.
Is there any advantage to this over mining from two+ plot files independently?
I suppose what I am asking here really is how much of an impact will dividing CPU and RAM usage between two mining instances affect the mining rate.
Is this as simple as it looks,
i.e.
1 miner runs at 100% of processing power provided.
2 miners run at 50% each of total processing provided over 2 separate plot ranges
,meaning that the efficiency is the same in both cases.
Thank you to anyone who takes the time to provide some answers here.
Ava
1. If you are trying to do sequential, you would do the former, since 10000000 numbers starting with 0 is 0 - 9999999. Like you correctly stated later though, starting point does not matter as long as you don't have ranges that overlap.
The miner rescans the folder for new files every block.
2. Ranges must not overlap, or you will pointlessly doing repeat work.
3. The miner only reads with one thread, so running one / drive will cause it to finish reading sooner. The miner doesn't need much processing power when using plot files, but it can tend to eat ram a bit.