Author

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

full member
Activity: 121
Merit: 100
why all exchanges don't add this good coin?
full member
Activity: 494
Merit: 100
Mined 6 blocks after 7 days..............
hero member
Activity: 518
Merit: 500
i wonder whether the passphrase ppl are using has any baring on the luck ppl are experiencing. i for one used lastpass to generate a 100 character passphrase consisting of only characters that look like random combination of words joined together.

I can assure you: The passphrase has nothing to do with your chances of finding a block.

About the GPU issue:
I've just finished an OpenCL-Test-Implementation. On an R280X it takes ~22s for 10k nonces, assuming the final hashes are pre-calculated. With a block time of 5 minutes that GPU equals ~35GB of disk space while consuming 200W of power. No real alternative.



Is this for the plot generation?
Of course. That speed is the same as mining with a 26.6GB plot file, except drawing significantly more electricity. It will however all you to generate plots at about 4.6 hours / TB

That's better than the cpu, currently at 200GB per 8~12 hours. I'd personally would use the gpu implementation.
sr. member
Activity: 280
Merit: 250
i wonder whether the passphrase ppl are using has any baring on the luck ppl are experiencing. i for one used lastpass to generate a 100 character passphrase consisting of only characters that look like random combination of words joined together.

I can assure you: The passphrase has nothing to do with your chances of finding a block.

About the GPU issue:
I've just finished an OpenCL-Test-Implementation. On an R280X it takes ~22s for 10k nonces, assuming the final hashes are pre-calculated. With a block time of 5 minutes that GPU equals ~35GB of disk space while consuming 200W of power. No real alternative.



Is this for the plot generation?
Of course. That speed is the same as mining with a 26.6GB plot file, except drawing significantly more electricity. It will however all you to generate plots at about 4.6 hours / TB
hero member
Activity: 518
Merit: 500
i wonder whether the passphrase ppl are using has any baring on the luck ppl are experiencing. i for one used lastpass to generate a 100 character passphrase consisting of only characters that look like random combination of words joined together.

I can assure you: The passphrase has nothing to do with your chances of finding a block.

About the GPU issue:
I've just finished an OpenCL-Test-Implementation. On an R280X it takes ~22s for 10k nonces, assuming the final hashes are pre-calculated. With a block time of 5 minutes that GPU equals ~35GB of disk space while consuming 200W of power. No real alternative.



Is this for the plot generation?
legendary
Activity: 2282
Merit: 1072
https://crowetic.com | https://qortal.org
ABC, I am still trying to figure out the asset thing, I did the trade and now I have 1 asset, then I just trade it on the exchange right? Cool. Be on the lookout for my next sends! Can I send you more than 1k at a time, what if I sent 8k?
- sure you can.  1K is just a minimum.

sounds good, be on the lookout, another 18k or so coming your way!

Hey man,  I sent the 18k to you quite a while back, as well as another message with my nxt ID... still haven't seen anything from your end... Let me know when this will happen. Much appreciated. Thanks!
newbie
Activity: 35
Merit: 0
I sent burst coins, sent arbitrary message , and after one hour, i receve nothing.
Sorry i ask, but i am not sure how this actually works.  Confirmations are 10+ what does it mean ? confirmed ? So where are all my coins? i can not see them at all...
please see: https://nxtblocks.info/#section/txid/8290271727934381987

This is transfer of 1000BURST assets to your account.  Also I've sent you 5 NXT to cover the fee of sell orders.

so you have fulfilled 1] from here: https://bitcointalksearch.org/topic/m.8381305

In order to sell your BURTS coins with Asset Exchange, you should:
1] Obtain 1000BURST asset for your BURST coins;
2] Place sell order with your newly 1000BURST asset at Nxt Asset Exchange (see public Nxt nodes below);
3] When somebody buy you 1000BURST asset, you'll get some NXT coins (according to your price);
4] Sell that NXT coins at https://www.cryptsy.com/ or keep them if you want.


now you should do  2], 3] and 4]

how to do 2] :
- goto your Nxt wallet
- goto Asset Exchange
- goto My Assets
- click 1000BURST on the right
- made Sell order(s)

ask question if you have.


but now i see 3 orders for buy

Account                                    Quantity    Price    Total
NXT-LKHJ-8DGS-HMBE-AL3N5           10          199   1'990
NXT-M5CR-UEFK-MEAJ-DT4AG          1           200   200
NXT-6Q74-9GCJ-46E7-7F5XJ            1           230   230

can i close 1 of them with my asset? if yes, how?
sr. member
Activity: 256
Merit: 250
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?
to generate the plots you require more cpu resources than for mining.
parsing the plotfiles also produces cpu load.
in most cases the cpu waits for the disk io but if your storage is fast enough the cpu may become the bottleneck.
i am running on a gbit network cluster filesystem providing constantly 30mb/s to the miner.
the miner consumes about 5% cpu load and 20-30% io waits.
this 5% relates to 8 threads which means the miner may use up to 12.5% cpu load before it becomes the bottleneck.
for a 4 minute blocktime my calculation says this setup works up to 16tb plots.
if the storage could provide more than 60mb/s the cpu of this setup is the bottleneck.
so before i have 16tb plots during the next days i have to redesign my storage layout to work with several miner instances.

newbie
Activity: 10
Merit: 0
WTS 330k Burst
PM me with an (reasonable) offer
newbie
Activity: 40
Merit: 0
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

CPU Power only Matters when generating Plots.


Another question by me:

The instance to generate plots with #myAdress #startingPlot #plotsToCreate #??? #Threads
That does the #??? Number stand for? And is it a problem, if some of my plots got different #???  numbers?
It's stagnation, really just how many plots it will generate before flushing to the disk. Higher number uses more RAM during plot generation, personally I use 1024, so I can get away with using 1gb RAM for the generation.

Perfect, thank you Smiley
newbie
Activity: 46
Merit: 0
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

CPU Power only Matters when generating Plots.


Another question by me:

The instance to generate plots with #myAdress #startingPlot #plotsToCreate #??? #Threads
That does the #??? Number stand for? And is it a problem, if some of my plots got different #???  numbers?
It's stagnation, really just how many plots it will generate before flushing to the disk. Higher number uses more RAM during plot generation, personally I use 1024, so I can get away with using 1gb RAM for the generation.
newbie
Activity: 40
Merit: 0
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

CPU Power only Matters when generating Plots.


Another question by me:

The instance to generate plots with #myAdress #startingPlot #plotsToCreate #??? #Threads
That does the #??? Number stand for? And is it a problem, if some of my plots got different #???  numbers?
member
Activity: 84
Merit: 10
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

Only important for generating plotfiles.
legendary
Activity: 1932
Merit: 1042
https://locktrip.com/?refId=40964
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?
sr. member
Activity: 256
Merit: 250
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

for the mining itself it may still be better to run several instances cause the plotfiles are read sequentially as i know.
so if you have a hash with a timeout of 15 seconds first seen after 100 seconds it may not be as useful as if its seen earlier ;-)
also if you are limited by ntfs to work with 2tb volumes the simplest solution is to run a miner instance for each volume instead of linking the plotfiles to a centralized location.

newbie
Activity: 46
Merit: 0
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
Since the miner only reads from a single directory, you either have to run an instance for every folder with plots (usually 1 per drive), or link them all into one folder.
full member
Activity: 227
Merit: 100
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
read above about "mklink"
sr. member
Activity: 336
Merit: 250
Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?
sr. member
Activity: 280
Merit: 250
The akka warning happens if you are still reading plot files when the client sees a new block. It's just warning that still ongoing stuff is being killed off, which is intended behaviour, since there's no point still mining on an old block.
sr. member
Activity: 256
Merit: 250
who knows what it is ?
Code:

{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b
0b52ae827b9c1ab6b95071a357f20d6fbae4c963f9782b26"}
[INFO] [08/18/2014 00:54:50.677] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [1] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [2] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [3] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.679] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [4] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [5] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [6] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [7] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [8] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [9] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [10] dead letters encountered, no more dead letters
 will be logged. This logging can be turned off or adjusted with configuration s
ettings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b

i don't know but i have same erro "akka" :-)

dev can you answer us?

thank you!
i get this also if the io load is high. i run with many 2gb files so its not such essential for me.
i think its a timeout setting in java to receive data.
check if your hdd has bad sectors.
Jump to: