anyone help me?
For all day i mine 2014-09-22 = 28.37191379 BURST
appr. 12Tb
my config:
{
"poolUrl" : "burst-eu.cryptomining.farm:8124",
"submissionMaxDelay" : 30,
"submissionMaxRetry" : 3,
"socketTimeout" : 60,
"plots" :
[
"G:\\plots",
"E:\\plots",
"I:\\plots",
"H:\\plots",
"D:\\plots",
"F:\\plots",
"J:\\plots"
]
}
Пoпpoбyй мaйнep мoeй peдaкции
https://www.dropbox.com/s/85cequgcmlonc6z/miner-burst.zip?dl=0cтpoкa зaпycкa в твoeм cлyчae:
miner.exe pool burst-eu.cryptomining.farm 8124 G:\plots\ E:\plots\ I:\plots\ H:\plots\ D:\plots\ F:\plots\ J:\plots\
my miner is not work well with single stagger, 409600 is quite large, miner need to allocate continuous 52MB on RAM for each plot, multiplied that by 8 plots of yours, it need 400MB
continous space, maybe it failed to do this, i can fix this but currently i dont have time yet
either you just use another miner (such as dcct's or java), or
dont do any modification (such as optimize) to your plot, just use stagger size of
4096 or 8192, you wont see any differences between optimized and un-optimized plot i think, because for example if you have 4 TB of plot, every 4 minutes miner only read 1 GB of those plot data and then its idle. doing disk seeks of 1GB
every 4 minutes (on average) wont kill your drive
and doing the read as fast as you can and then submit it to pool as fast as you can will only do
more harm than good for your earning, and useless since the miner will randomly delay the submission, without this delay there is good chance you got failed on nonce submission due to spike in pool's deadline processing, its because all pools based on my source dont have deadline limit, we accept all nonces and calculate that nonce into deadline, if everyone submitting nonce as fast as they can, then during every new block pool is flooded with nonce submission and most of them are crap nonce resulting in months or years of deadline