Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1240. (Read 2170889 times)

thx for help, so they are useless, I should delete them, or can I rename the files and the bat's used?

All of them are going to overlap...

One drive needs to be 0 204800
next drive 204801 1004801
next drive 1004802 4204802
and lastly 4204803 7404803

that way your plots are all for the same account #, but are all spaced out and will have the greatest possibility of generating a block...

kinda what I suspected.
the 800000 and 80000000?

how i can start generate plat on next HDD?

Cent Os

2-nd HDD mount on

/mnt/disk1/

not quite sure but it looks like u have plots over lapping

can someone please advise on these plots settings on my primary pc:

1097082171119035817_0_204800_1000
1097082171119035817_1_800000_500
1097082171119035817_1_3200000_500 (still plotting after 2+ days)
1097082171119035817_1_80000000_500 (still plotting after 2+ days)

thinking I error'd in these plot settings, maybe I need to redo...?

i have mined since start.finally finsished plotting 1.8 TB hard drive today and i have found 32 blocks

If anyone is interested, the conclusion of my test to see if I could speed up plot generation by farming it out using cluster/cloud computing is:
Yes it can be done, but it is probably not worth it.  This is what I did using Amazon EC2...

First I created a single instance (2 core) to act as the server for the plot storage and also act as the wallet server / miner.
This instance had a 1TB Elastic Block Store volume attached to it (1TB is max EBS volume size on AWS). I made this volume available to the network using NFS

I then created a "plot generator" instance with much higher CPU capacity (C3.xlarge 8 core). I mounted the shared volume so it appeared like a local disk and started creating 10GB plots
I then created a few scripts so that upon startup the instance would auto-mount the NFS volume, figure out what the last used nonce range was, and start mining from the next 10GB plot
Finally, I created an image of this instance and spooled up 100 more instances like it (spot rates, nice and cheap).

To begin with it all looked great but I soon hit the bandwidth limit of the instance I was using as the server.  In essence the server didn't have enough network bandwidth to cope with all of the data being copied to it.  This restricted plot creation to a little over 100GB / hour.  Changing the instance type of the server instance to one with a "high" network performance got this up to around 400 GB/hour.  If I had have left it running I would have created all 1 TB of plots in 2.5 hours, at a cost of around $20.  This could have been repeated or even parallelized to create several 1TB volumes full of plots in a relatively short amount of time.

After all the fiddling about getting it working, I spent around $70 testing this stuff out, only to conclude it was too much hassle.  And as OP said earlier, the cost of EBS storage on AWS is too high to make this a viable long term mining option.  That said, had I have done all of this on day one, I would have scaled the process out and had 10TB+ up within the first few hours and dominated the mining.  Good to know I have the process licked for the next PoC coin

Unfortunately I STILL don't have any BURST as I don't have any spare capacity at home so haven't been able to mine at all  So if anyone would like to donate some coins to offset the cost of testing all of this, my address is BURST-WADY-CBZE-HSJU-2NH5G

Many thanks!