Author

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

sr. member
Activity: 334
Merit: 250
🌟 æternity🌟 blockchain🌟
My miner is still crashing twice in a day. Always dead letters problem. As suggested by a kind fellow here, i have placed this as the bat file.

Code:
C:\Windows\SysWOW64\java -Xmx1024m -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121

But it still crashed. I have 2 miners running, one is in internal hard disk and another external. The external one always crash with dead letters. A little help pls  Sad
if close your internal miner and open external one only, if external one not crash any more, that is your memory is not enough to open 2 miners. change your -Xmx1024m to -Xmx500m and try again

will reducing the parameter to 500m reduce the mining performance? If yes then i'll off my internal one because it's only 200GB where as my external one is 4TB
full member
Activity: 238
Merit: 100
My miner is still crashing twice in a day. Always dead letters problem. As suggested by a kind fellow here, i have placed this as the bat file.

Code:
C:\Windows\SysWOW64\java -Xmx1024m -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121

But it still crashed. I have 2 miners running, one is in internal hard disk and another external. The external one always crash with dead letters. A little help pls  Sad
if close your internal miner and open external one only, if external one not crash any more, that is your memory is not enough to open 2 miners. change your -Xmx1024m to -Xmx500m and try again
full member
Activity: 224
Merit: 100
That's a really good "getting started" guide. Thank you for your work Smiley

No problem, I'm glad to help! I you have any input let me know and I will update it.

Also, it seems that calculation of nonces/minute may be off...
https://bitcointalksearch.org/topic/m.8771161

It shows me calculating at 121,230 nonces/minute... but actual file growth is more along the lines of only 12,123.0 nonces/minute.
(Maybe this is from the message I got when compiling?)

...It might also be nice to have a "ETA" for completion time. But not really needed.

Maybe the CLOCKS_PER_SEC value doesn't match the actual clock() values on your platform (function that I use to retrieve the time). I will use the time() function instead.

Here is the new version:

GPU plot generator v2.0.1

Warning: to the AMD owners, the 14.4 catalyst driver cause a major bug. The generated files are corrupted. I will investigate on this problem. In the meantime, I recommend you to switch back your driver to the 13.12 version.

Changelog:
- Nonces display corrected (XX/YY nonces).
- Using time() function rather than clock() in nonces/minute computation.
- Nonces/minutes repeated at the end of the generation process to keep a trace of it after execution.
- ETA and elapsed time added.

Windows x86 binaries: https://mega.co.nz/#!TVEVjQ5L!Uyd2HuPTZSP9eARwjiChjd1P6BMWHQtYT0SGGHLrnuI
Sources: https://mega.co.nz/#!2RUwHAyC!IOxfTZk9PsRdPS7Z3a76MAT4vT3ygvp--r_dVQ5GaD4
how i can check my plots at corrupt?
sr. member
Activity: 334
Merit: 250
🌟 æternity🌟 blockchain🌟
My miner is still crashing twice in a day. Always dead letters problem. As suggested by a kind fellow here, i have placed this as the bat file.

Code:
C:\Windows\SysWOW64\java -Xmx1024m -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121

But it still crashed. I have 2 miners running, one is in internal hard disk and another external. The external one always crash with dead letters. A little help pls  Sad
donator
Activity: 2352
Merit: 1060
between a rock and a block!
so all the plot files generated with 2.0.0 are all corrupt then?  how to tell for sure?

That's a really good "getting started" guide. Thank you for your work Smiley

No problem, I'm glad to help! I you have any input let me know and I will update it.

Also, it seems that calculation of nonces/minute may be off...
https://bitcointalksearch.org/topic/m.8771161

It shows me calculating at 121,230 nonces/minute... but actual file growth is more along the lines of only 12,123.0 nonces/minute.
(Maybe this is from the message I got when compiling?)

...It might also be nice to have a "ETA" for completion time. But not really needed.

Maybe the CLOCKS_PER_SEC value doesn't match the actual clock() values on your platform (function that I use to retrieve the time). I will use the time() function instead.

Here is the new version:

GPU plot generator v2.0.1

Warning: to the AMD owners, the 14.4 catalyst driver cause a major bug. The generated files are corrupted. I will investigate on this problem. In the meantime, I recommend you to switch back your driver to the 13.12 version.

Changelog:
- Nonces display corrected (XX/YY nonces).
- Using time() function rather than clock() in nonces/minute computation.
- Nonces/minutes repeated at the end of the generation process to keep a trace of it after execution.
- ETA and elapsed time added.

Windows x86 binaries: https://mega.co.nz/#!TVEVjQ5L!Uyd2HuPTZSP9eARwjiChjd1P6BMWHQtYT0SGGHLrnuI
Sources: https://mega.co.nz/#!2RUwHAyC!IOxfTZk9PsRdPS7Z3a76MAT4vT3ygvp--r_dVQ5GaD4
sr. member
Activity: 462
Merit: 250
Haha, I got the GPU ploter working on an internal laptop card  Grin

Intel HD Graphics 4000 - 750 nonces/minutes so far and increasing. Beware AMD owners Wink


On a more serious note: on a box with decent hardward, running one miner on it's three disk's. Just recently I've gotten the following error:

"Error: Unable to get mining info from wallet"

I've upgraded to the latest wallet and its running. One one know what's up...? The only extradorinary is that is moving two file around 500gb between computers, but Filzilla take so litte resources I can't thing it does matter do the wallet error.

Any ideas?

sr. member
Activity: 307
Merit: 250
Plotted 28 TB. Average 21K burst per day at rate of 0.00000330 BTC with 0.0693 BTC Profit sent to BTC-E. POC is wonderful.

9 TB more to complete a total of 8 HDD Plot.  Smiley

Ordered another 12 HDD (Seagate Desktop HDD 6TB 7200RPM STBD6000100) from Amazon. Should receive it next week so I'm still have time to setup 2 new PCs station with each to handle 6 HDD.




Not profit if you just ordered 12 HDDs!

It's profitable since HDD's are easily resellable.
k
sr. member
Activity: 462
Merit: 250
After issuing the last command, it just returns to a prompt... no additional output. I assume this means the plot files match.
(also I am mining and finding shares from the GPU plot as well)

Thank you.  The 121k nonces/min had me worried there.
member
Activity: 364
Merit: 10
https://bchain.info/BURST/tools/calculator  lying or pool v1 has problems. Yesterday calculator = 20 000, at fact on v1 = 12000. Whats problem?

Pool is having issues as well.

you too on v1?

I was. I wasn't getting expected payouts so I decided to launch a private pool.
full member
Activity: 152
Merit: 100
https://bchain.info/BURST/tools/calculator  lying or pool v1 has problems. Yesterday calculator = 20 000, at fact on v1 = 12000. Whats problem?

Pool is having issues as well.

you too on v1?
member
Activity: 364
Merit: 10
https://bchain.info/BURST/tools/calculator  lying or pool v1 has problems. Yesterday calculator = 20 000, at fact on v1 = 12000. Whats problem?

Pool is having issues as well.
full member
Activity: 238
Merit: 100
https://bchain.info/BURST/tools/calculator  lying or pool v1 has problems. Yesterday calculator = 20 000, at fact on v1 = 12000. Whats problem?
it is not accurate, it is estimated by the difficulty and difficulty changed with the time
full member
Activity: 152
Merit: 100
https://bchain.info/BURST/tools/calculator  lying or pool v1 has problems. Yesterday calculator = 20 000, at fact on v1 = 12000. Whats problem?
sr. member
Activity: 462
Merit: 250
Great, thanke Smiley

Any similar code for the wallet available...?


Windows
Code:
@echo off
cls
:start
java -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://poolipgoeshere:8121
goto start

Linux
Code:
while i="0"
do
java -cp pocminer_pool.jar:lib/*:lib/akka/*:lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://poolipgoeshere:8121
done

 Grin
Was just about to post this for Windows Tongue


If I close the cmd that starts mining with the windows .bat with the above in it, then nothing opens back up.  How am I supposed to implement it?

Thanks!

If you close yourself it won't restart, but if it closes itself, then it restarts!! Just test it out.
member
Activity: 364
Merit: 10
Would anyone be interested in a buying shares of a mining operation? We currently are plotting 48tb with another 48tb coming in soon.
member
Activity: 364
Merit: 10
Plotted 28 TB. Average 21K burst per day at rate of 0.00000330 BTC with 0.0693 BTC Profit sent to BTC-E. POC is wonderful.

9 TB more to complete a total of 8 HDD Plot.  Smiley

Ordered another 12 HDD (Seagate Desktop HDD 6TB 7200RPM STBD6000100) from Amazon. Should receive it next week so I'm still have time to setup 2 new PCs station with each to handle 6 HDD.




Not profit if you just ordered 12 HDDs!

It's profitable since HDD's are easily resellable.
sr. member
Activity: 307
Merit: 250
Plotted 28 TB. Average 21K burst per day at rate of 0.00000330 BTC with 0.0693 BTC Profit sent to BTC-E. POC is wonderful.

9 TB more to complete a total of 8 HDD Plot.  Smiley

Ordered another 12 HDD (Seagate Desktop HDD 6TB 7200RPM STBD6000100) from Amazon. Should receive it next week so I'm still have time to setup 2 new PCs station with each to handle 6 HDD.




Not profit if you just ordered 12 HDDs!
full member
Activity: 494
Merit: 100
Plotted 28 TB. Average 21K burst per day at rate of 0.00000330 BTC with 0.0693 BTC Profit sent to BTC-E. POC is wonderful.

9 TB more to complete a total of 8 HDD Plot.  Smiley

Ordered another 12 HDD (Seagate Desktop HDD 6TB 7200RPM STBD6000100) from Amazon. Should receive it next week so I'm still have time to setup 2 new PCs station with each to handle 6 HDD.


member
Activity: 60
Merit: 10
Code:
head -c `stat -c%s ` o-path | diff - 

should work.  Where o-path is the path to the old output, and n-path is the path to the new.
Seriously though, I have no idea what you are requesting.

If you're still running a plot on the GPU, could you then try running one of the CPU plotters with the same parameters (address, nonce range, stagger size) for a few minutes and check that they match in the part created by the CPU plotter?  Say the directory containing the GPU plotter output (the "plots" directory") is , and the path to the CPU output is .  Could you then run this command in a terminal and report back its output?  If they match, there should be no output.

Code:
head -c `stat -c%s `  | diff - 
Gotcha.
I'll take a look into testing this tomorrow. Once the GPU plot I have going currently finishes.

I didn't forget... Plot file just finished.

I ran your test with some smaller plot files:
Warning: to the AMD owners, the 14.4 catalyst driver cause a major bug. The generated files are corrupted. I will investigate on this problem. In the meantime, I recommend you to switch back your driver to the 13.12 version.
My plots appear to be fine (on Linux) generated with the 14.4 catalyst driver, as compared to the same plot generated with the CPU

I'll test out v2.0.1 and see if there are any changes.
[/quote]

That's a good news, even if I will have to investigate more on this part ^^

For those who already generated some files with the plotter, to make sure the generation is successful, do the following :
Generate a file with the same parameters as your full plot file (address + offset + stagger) but with a noncesNumber of 1.
The generated file has to match with the first bytes of your full file.
member
Activity: 60
Merit: 10
That's a really good "getting started" guide. Thank you for your work Smiley

No problem, I'm glad to help! I you have any input let me know and I will update it.

Also, it seems that calculation of nonces/minute may be off...
https://bitcointalksearch.org/topic/m.8771161

It shows me calculating at 121,230 nonces/minute... but actual file growth is more along the lines of only 12,123.0 nonces/minute.
(Maybe this is from the message I got when compiling?)

...It might also be nice to have a "ETA" for completion time. But not really needed.

Maybe the CLOCKS_PER_SEC value doesn't match the actual clock() values on your platform (function that I use to retrieve the time). I will use the time() function instead.

Here is the new version:

GPU plot generator v2.0.1

Warning: to the AMD owners, the 14.4 catalyst driver cause a major bug. The generated files are corrupted. I will investigate on this problem. In the meantime, I recommend you to switch back your driver to the 13.12 version.

Changelog:
- Nonces display corrected (XX/YY nonces).
- Using time() function rather than clock() in nonces/minute computation.
- Nonces/minutes repeated at the end of the generation process to keep a trace of it after execution.
- ETA and elapsed time added.

Windows x86 binaries: https://mega.co.nz/#!TVEVjQ5L!Uyd2HuPTZSP9eARwjiChjd1P6BMWHQtYT0SGGHLrnuI
Sources: https://mega.co.nz/#!2RUwHAyC!IOxfTZk9PsRdPS7Z3a76MAT4vT3ygvp--r_dVQ5GaD4

So, this is just a cosmetic update? I don't know if it's just me, but my system would use 3GB total in the first 6 hours. Then later on, it would use double at 6~6.5GB and degradation of speed also. Is it possible there is a memory leak in the plotter? I'm running AMD 13.9 driver with 2.9.1 APP SDK.

Yes this is a minor update.
I'm working on a major update right now:
I'm trying to remove the final scoops re-ordering from the kernel to run it in pure CPU mode. This will remove the x2 GPU RAM overhead. I'm also trying to decorrelate the staggerSize and the necessary RAM amount (note that this will increase I/O operations when writting nonces to disk, but I'll give it a try. If it works well, we would be able to go to staggerSize=totalNoncesNumber).
I'm also reducing the cost of the step2 kernel to enhance nonces/minute.
With all of those improvements, it will be easier to make the multi-gpu aware version of the plotter.
Jump to: