[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[lmaonade80]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Memory doesn't really help - the miner itself uses very little memory, it's windows trying to be "helpful" and cache the data from the drives that sucks up the ram, enable the "cleanmem" setting and all memory will be retruned after the mining process. Add more memory and windows will just suck up more, until you force it to be released.

The problem issue you can run into, especially when mining multiple drives, is that you max out the CPU. Blagos miner will use one core/thread per drive/directory you specify. If you're mining with more drives than you have threads, your CPU will be maxed out. To get around this you can adjust the CPU affinity to leave some of the cores untouched by the miner - generally I allow the miner to use all but one thread. You can either do it manually by going into task manager -> processes, right clicking miner.exe, select Set Affinity, and unselect CPU 0. If you're launching it from a batch file, you can set the affinity in the batch file.

To do it via the batch file, do:  start "Burst Miner" /wait /affinity <affinity_mask> miner

The affinity mask is a hex representation of a binary value of your cpus. eg, if you have four threads, the binary mask is XXXX, where X is 0 or 1 - 0 means don't use that CPU, 1 means use it. So on a 4 thread CPU, to disable CPU0 for miner, the binary vale would be 1110, which is 0xE. So the command would be:

start "Burst Miner" /wait /affinity 0xD miner

For a 8 thread CPU, it'd be 1111 1110, => 0xFE, so start "Burst Miner" /wait /affinity 0x0FE miner

To leave two threads available:

start "Burst Miner" /wait /affinity 0xFD miner

Windows calc.exe has a programmers mode that can do the binary -> hex conversions for the hexidecimally challenged ;-)

H.

Thanks! That was helpful in regards to my CPU. My question in regards to RAM usage is still the problem. Resource manager watches my RAM fill up until I can no longer operate my computer. Unless I've misread your post, all your help was in use to my CPU, which does not run into any issues.

Could you elaborate on this "cleanmem" setting, and if I read your post correctly, it is only helpful BEFORE and AFTER mining process and not DURING, so my only real correction is using a new Windows OS, or is there clearing of the ram during the mining process I can write in?

The file caching shouldn't impact your usage, over time it can cause performance issues, but with the memory cleaning it's mostly resolved. during the mining process windows will use pretty much all available memory for caching, but it will not swap out other apps to make space for caching. On my daily PC, which is mining, memory usage during mining goes from around 4GB to just short of the 18GB installed, and I can't tell when mining is happening.

The memory clean does clean out everything that's cached, so that can impact your performance, but not to the level of your CPU getting maxed. To use the cleanmem setting, make sure you have Blagos latest miner, and have in your miner.conf

  "UseCleanMem" : true,

Miner is available from: https://github.com/Blagodarenko/miner-burst/releases/download/v1.150401/miner-burst-1.150401.zip

H.

Unfortunately, none of this solved my issue. The miner eats up RAM like nobody's business. I'll keep looking for realtime cache-clearing solutions in my free time, but it looks like I'm SOL until Win10 for burst and my 17 TB.

[haitch]

idk.. maybe it's not worth it.  Question is, how long does it take to verify a hash and does making it 500 to 1000 times faster to verify a block significantly decrease DDOS attack risk?  What about how long would it take to verify a couple years worth of block headers?  Burstdev did come up with an interesting way to essentially checkpoint our chain so that customers could only download one blockheader per week.. maybe that fixes the problem and this is no longer needed

So, to me the most important number is, how long does it take to do 4096 Shabal256's vs 1 Shabal256.  Anyone have a precise number?

GPU Plotting I can do about 30K nonces/min on a single GPU, which is about 122M shabal256/min.

Scaling that down,a single shabal256 takes 0.00000048828125 seconds, and 4096 take 0.002 seconds.

H.

[FakeAccount]

yes i also think so. got 3 miner, all win 8 and one has it every 5 days, the other 2 never had it until now.

if everything is the same, then maybe it's now trying to execute some code it hasn't tried/needed to run before.
some variable changed in size?  i'm just thinking out loud here.

for me the error message sounds like a wrong index somewhere in the code.
maybe the cache filling thread doesn't get reset correctly on block change if the sata port or network times out and freezes the whole machine.
there may be included libraries which tend to crash the program if threads get simply terminated and not shutdown.
on average situations this works but if there are long response times somewhere (disk or network) the regular situation changes and a counter wont be reset (multithreading can be evil).

personally i have not reviewed the code to give a hint where to look for.
simply switch your rigs to linux using the dcct or java miner.
both combinations run totally unattended (except the wallet updates) without any of the windows related issues since month for me
even the  last wallet update did not crash a single running miner instance.

what is special with the blago miner?
how many tb can be parsed per core per minute on a current average i7 cpu?
is it only useful for windows based mining?

some ppl don't have time to learn Linux.

I have win 10, it runs flawlessly now.

machine 1 (i7-5960X):
22:14:21 Thread "M:\plots" in 31.4 sec (22.2 MB/s) CPU 98.82%
22:14:21 Thread "N:\plots" in 31.5 sec (22.2 MB/s) CPU 99.15%
22:14:21 Thread "Q:\plots" in 31.5 sec (22.1 MB/s) CPU 99.14%
22:14:22 Thread "P:\plots" in 31.7 sec (22.0 MB/s) CPU 98.65%
22:14:22 Thread "O:\plots" in 31.8 sec (21.9 MB/s) CPU 99.09%
22:14:30 Thread "L:\plots" in 40.1 sec (23.2 MB/s) CPU 99.37%
22:14:31 Thread "V:\plots" in 41.3 sec (22.5 MB/s) CPU 97.65%
22:14:47 Thread "H:\plots" in 57.2 sec (24.4 MB/s) CPU 99.21%
22:14:47 Thread "Y:\plots" in 57.5 sec (24.3 MB/s) CPU 97.72%
22:14:47 Thread "J:\plots" in 57.6 sec (24.2 MB/s) CPU 98.99%
22:14:47 Thread "I:\plots" in 57.7 sec (24.2 MB/s) CPU 99.24%
22:14:48 Thread "S:\plots" in 58.0 sec (24.1 MB/s) CPU 98.14%
22:15:03 Thread "F:\plots" in 73.1 sec (25.5 MB/s) CPU 98.57%
22:15:03 Thread "K:\plots" in 73.2 sec (25.4 MB/s) CPU 98.39%
22:15:03 Thread "G:\plots" in 73.2 sec (25.4 MB/s) CPU 98.38%
100% 72596 GB. DL=61361 sdl:5083(0) cdl:5083(0) ss:548(0) rs:548(0)

machine 2 (AMD 8350 8 cores):
22:14:22 Thread "F:\plots" in 32.7 sec (21.3 MB/s) CPU 97.85%
22:14:22 Thread "G:\plots" in 32.7 sec (21.3 MB/s) CPU 98.09%
22:14:48 Thread "J:\plots" in 59.0 sec (19.7 MB/s) CPU 98.17%
22:14:49 Thread "H:\plots" in 59.7 sec (19.5 MB/s) CPU 95.62%
22:14:53 Thread "L:\plots" in 64.2 sec (21.7 MB/s) CPU 98.55%
22:14:58 Thread "D:\plots" in 68.7 sec (20.3 MB/s) CPU 98.70%
22:14:58 Thread "M:\plots" in 68.8 sec (20.3 MB/s) CPU 98.68%
22:15:12 Thread "K:\plots" in 82.5 sec (22.6 MB/s) CPU 98.31%
22:15:16 Thread "E:\plots" in 86.8 sec (21.5 MB/s) CPU 98.83%
100% 47024 GB. DL=53045 sdl:5746(0) cdl:5736(0) ss:138(0) rs:138(0)

[haitch]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Memory doesn't really help - the miner itself uses very little memory, it's windows trying to be "helpful" and cache the data from the drives that sucks up the ram, enable the "cleanmem" setting and all memory will be retruned after the mining process. Add more memory and windows will just suck up more, until you force it to be released.

The problem issue you can run into, especially when mining multiple drives, is that you max out the CPU. Blagos miner will use one core/thread per drive/directory you specify. If you're mining with more drives than you have threads, your CPU will be maxed out. To get around this you can adjust the CPU affinity to leave some of the cores untouched by the miner - generally I allow the miner to use all but one thread. You can either do it manually by going into task manager -> processes, right clicking miner.exe, select Set Affinity, and unselect CPU 0. If you're launching it from a batch file, you can set the affinity in the batch file.

To do it via the batch file, do:  start "Burst Miner" /wait /affinity <affinity_mask> miner

The affinity mask is a hex representation of a binary value of your cpus. eg, if you have four threads, the binary mask is XXXX, where X is 0 or 1 - 0 means don't use that CPU, 1 means use it. So on a 4 thread CPU, to disable CPU0 for miner, the binary vale would be 1110, which is 0xE. So the command would be:

start "Burst Miner" /wait /affinity 0xD miner

For a 8 thread CPU, it'd be 1111 1110, => 0xFE, so start "Burst Miner" /wait /affinity 0x0FE miner

To leave two threads available:

start "Burst Miner" /wait /affinity 0xFD miner

Windows calc.exe has a programmers mode that can do the binary -> hex conversions for the hexidecimally challenged ;-)

H.

Thanks! That was helpful in regards to my CPU. My question in regards to RAM usage is still the problem. Resource manager watches my RAM fill up until I can no longer operate my computer. Unless I've misread your post, all your help was in use to my CPU, which does not run into any issues.

Could you elaborate on this "cleanmem" setting, and if I read your post correctly, it is only helpful BEFORE and AFTER mining process and not DURING, so my only real correction is using a new Windows OS, or is there clearing of the ram during the mining process I can write in?

The file caching shouldn't impact your usage, over time it can cause performance issues, but with the memory cleaning it's mostly resolved. during the mining process windows will use pretty much all available memory for caching, but it will not swap out other apps to make space for caching. On my daily PC, which is mining, memory usage during mining goes from around 4GB to just short of the 18GB installed, and I can't tell when mining is happening.

The memory clean does clean out everything that's cached, so that can impact your performance, but not to the level of your CPU getting maxed. To use the cleanmem setting, make sure you have Blagos latest miner, and have in your miner.conf

  "UseCleanMem" : true,

Miner is available from: https://github.com/Blagodarenko/miner-burst/releases/download/v1.150401/miner-burst-1.150401.zip

H.

Unfortunately, none of this solved my issue. The miner eats up RAM like nobody's business. I'll keep looking for realtime cache-clearing solutions in my free time, but it looks like I'm SOL until Win10 for burst and my 17 TB.

I mine 90TB on a 32GB machine (server 2012) and with one CPU excluded, and I can't even tell when I'm mining.

I mine 10TB on a 18GB Win 7 machine I use all day/night with one CPU excluded, and I can't even tell when I'm mining.

https://www.dropbox.com/s/ev3f5e009hvn1lc/memusage.jpg?dl=0

[FakeAccount]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

i switched to win 10. all issues you are experiencing are gone with win 10.

[FakeAccount]

You're all idiots for wasting your time and money on this shitcoin that will never amount to anything.

stealing, cheatin thieving waste of water and biomass

[Grim]

machine 1 (i7-5960X):
22:14:21 Thread "M:\plots" in 31.4 sec (22.2 MB/s) CPU 98.82%
22:14:21 Thread "N:\plots" in 31.5 sec (22.2 MB/s) CPU 99.15%
22:14:21 Thread "Q:\plots" in 31.5 sec (22.1 MB/s) CPU 99.14%
22:14:22 Thread "P:\plots" in 31.7 sec (22.0 MB/s) CPU 98.65%
22:14:22 Thread "O:\plots" in 31.8 sec (21.9 MB/s) CPU 99.09%
22:14:30 Thread "L:\plots" in 40.1 sec (23.2 MB/s) CPU 99.37%
22:14:31 Thread "V:\plots" in 41.3 sec (22.5 MB/s) CPU 97.65%
22:14:47 Thread "H:\plots" in 57.2 sec (24.4 MB/s) CPU 99.21%
22:14:47 Thread "Y:\plots" in 57.5 sec (24.3 MB/s) CPU 97.72%
22:14:47 Thread "J:\plots" in 57.6 sec (24.2 MB/s) CPU 98.99%
22:14:47 Thread "I:\plots" in 57.7 sec (24.2 MB/s) CPU 99.24%
22:14:48 Thread "S:\plots" in 58.0 sec (24.1 MB/s) CPU 98.14%
22:15:03 Thread "F:\plots" in 73.1 sec (25.5 MB/s) CPU 98.57%
22:15:03 Thread "K:\plots" in 73.2 sec (25.4 MB/s) CPU 98.39%
22:15:03 Thread "G:\plots" in 73.2 sec (25.4 MB/s) CPU 98.38%
100% 72596 GB. DL=61361 sdl:5083(0) cdl:5083(0) ss:548(0) rs:548(0)

machine 2 (AMD 8350 8 cores):
22:14:22 Thread "F:\plots" in 32.7 sec (21.3 MB/s) CPU 97.85%
22:14:22 Thread "G:\plots" in 32.7 sec (21.3 MB/s) CPU 98.09%
22:14:48 Thread "J:\plots" in 59.0 sec (19.7 MB/s) CPU 98.17%
22:14:49 Thread "H:\plots" in 59.7 sec (19.5 MB/s) CPU 95.62%
22:14:53 Thread "L:\plots" in 64.2 sec (21.7 MB/s) CPU 98.55%
22:14:58 Thread "D:\plots" in 68.7 sec (20.3 MB/s) CPU 98.70%
22:14:58 Thread "M:\plots" in 68.8 sec (20.3 MB/s) CPU 98.68%
22:15:12 Thread "K:\plots" in 82.5 sec (22.6 MB/s) CPU 98.31%
22:15:16 Thread "E:\plots" in 86.8 sec (21.5 MB/s) CPU 98.83%
100% 47024 GB. DL=53045 sdl:5746(0) cdl:5736(0) ss:138(0) rs:138(0)

your read speed is quite low: 20 to 25 MB/s ...
too many hdds not enough true cores 

[koko2530]

CryptominingFarm Update

Solarfarm(CELL) Mining Pool
burst asset id : 11330004142522539040


URL : http://cell.cryptomining.farm
Recipient: BURST-4PFU-SPUL-327R-63KYJ
Port : 8124

Mining Calculator 10TB : 60-100 CELL per day

Join now !!
Get some shares of "Photovoltaic power station" by  your harddisk

[lmaonade80]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

i switched to win 10. all issues you are experiencing are gone with win 10.

Based on haitch's observations, it would appear my 2.8 ghz i5 is not enough CPU juice to power 5 4 GB HD's, and the RAM maxing out is background noise; Windows would free up the cache RAM as it needed it. The maxing out of RAM and unresponsiveness of the computer was just coincidental, I suppose.

If I come across a copy of Win8 or 10, I'll give it another shot, but I'm being told its my CPU.

[Blago]

question:

<...>
* for merged(optimized) plots miner read by 64*CacheSize bytes. For unmerged plots - by 64*stagger bytes.
<...>

can you explain how this is determined? is it as simple as reading the file name to see of nonces=stagger size?

Yes, miner compare filename's nonces and stagger.
https://github.com/Blagodarenko/miner-burst/blob/master/miner.cpp#L1690

This is done so that at one time would have read all the information available in part of plot.
for example, i have:
1) xxxx_yyyy_40000_4000
2) xxxx_yyyy_40960_4096
so, if i sets CacheSize = 4000, then 1) = 10 seeks, 2) = 11 seeks. And read by 64 bytes.
Now, miner reads all 64*stagger bytes, 1) = 10 seeks, 2) = 10 seeks.

Hi blago,

what do you recommend to set the cachesize to?

xxxx_yyyy_2048000_2048000
xxxx_yyyy_1024000_1024000
xxxx_yyyy_332800_332800
xxxx_yyyy_1433600_51200

This depends on the CPU performance and the number of cores therein.
try a few options:
"CacheSize": 51200
"CacheSize": 5120
"CacheSize": 25600
"CacheSize": 2560

the best option - it is when the thread ends earlier in time

[Chesteer]

http://crystaldigest.com/wp-content/uploads/2014/09/Jobs-For-Designers-crystal-digest.jpeg

Hi guys,

We're looking for graphic designer for our BURST team. We need some graphics for website, PR doc template, important tweets and much more.

If you're interested in working with us (or you know the right person) please feel free to contact with us:
 burst@countermail.com

or just pm me or mmmaybe.


Remember! We need to work together to make whole world hear about BURST  

[lmaonade80]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Memory doesn't really help - the miner itself uses very little memory, it's windows trying to be "helpful" and cache the data from the drives that sucks up the ram, enable the "cleanmem" setting and all memory will be retruned after the mining process. Add more memory and windows will just suck up more, until you force it to be released.

The problem issue you can run into, especially when mining multiple drives, is that you max out the CPU. Blagos miner will use one core/thread per drive/directory you specify. If you're mining with more drives than you have threads, your CPU will be maxed out. To get around this you can adjust the CPU affinity to leave some of the cores untouched by the miner - generally I allow the miner to use all but one thread. You can either do it manually by going into task manager -> processes, right clicking miner.exe, select Set Affinity, and unselect CPU 0. If you're launching it from a batch file, you can set the affinity in the batch file.

To do it via the batch file, do:  start "Burst Miner" /wait /affinity <affinity_mask> miner

The affinity mask is a hex representation of a binary value of your cpus. eg, if you have four threads, the binary mask is XXXX, where X is 0 or 1 - 0 means don't use that CPU, 1 means use it. So on a 4 thread CPU, to disable CPU0 for miner, the binary vale would be 1110, which is 0xE. So the command would be:

start "Burst Miner" /wait /affinity 0xD miner

For a 8 thread CPU, it'd be 1111 1110, => 0xFE, so start "Burst Miner" /wait /affinity 0x0FE miner

To leave two threads available:

start "Burst Miner" /wait /affinity 0xFD miner

Windows calc.exe has a programmers mode that can do the binary -> hex conversions for the hexidecimally challenged ;-)

H.

Thanks! That was helpful in regards to my CPU. My question in regards to RAM usage is still the problem. Resource manager watches my RAM fill up until I can no longer operate my computer. Unless I've misread your post, all your help was in use to my CPU, which does not run into any issues.

Could you elaborate on this "cleanmem" setting, and if I read your post correctly, it is only helpful BEFORE and AFTER mining process and not DURING, so my only real correction is using a new Windows OS, or is there clearing of the ram during the mining process I can write in?

The file caching shouldn't impact your usage, over time it can cause performance issues, but with the memory cleaning it's mostly resolved. during the mining process windows will use pretty much all available memory for caching, but it will not swap out other apps to make space for caching. On my daily PC, which is mining, memory usage during mining goes from around 4GB to just short of the 18GB installed, and I can't tell when mining is happening.

The memory clean does clean out everything that's cached, so that can impact your performance, but not to the level of your CPU getting maxed. To use the cleanmem setting, make sure you have Blagos latest miner, and have in your miner.conf

  "UseCleanMem" : true,

Miner is available from: https://github.com/Blagodarenko/miner-burst/releases/download/v1.150401/miner-burst-1.150401.zip

H.

Unfortunately, none of this solved my issue. The miner eats up RAM like nobody's business. I'll keep looking for realtime cache-clearing solutions in my free time, but it looks like I'm SOL until Win10 for burst and my 17 TB.

I mine 90TB on a 32GB machine (server 2012) and with one CPU excluded, and I can't even tell when I'm mining.

I mine 10TB on a 18GB Win 7 machine I use all day/night with one CPU excluded, and I can't even tell when I'm mining.

https://www.dropbox.com/s/ev3f5e009hvn1lc/memusage.jpg?dl=0

Mining with Runaurufu's miner with no problems; all 17 TB's. I'll have to check to make sure that all the TB's show up in the pool tomorrow since this miner is a bit crude. I still believe it is a RAM issue.

[muhrohmat]

i realize theres big rollers and miners here i only have 5,4 TB and im not mining now its lags the prcessing a bit the blago miner soo i will stable after a new computer for that but the fork maight pass me by the 92000 blocks one

[mmmaybe]

As we promised total transparency regarding donation spending, I'll like to info that chesteer was given 25K for extraordinary work in the Team

You find the spending reports here: https://burstforum.com/index.php?threads/donate-to-the-dev-team-edit-20th-april-2015.783/

On the same time, chesteer donated 25,000 BURST So now we got a streak going again with donations - three days with new donating Thanks!

[FakeAccount]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

i switched to win 10. all issues you are experiencing are gone with win 10.

Based on haitch's observations, it would appear my 2.8 ghz i5 is not enough CPU juice to power 5 4 GB HD's, and the RAM maxing out is background noise; Windows would free up the cache RAM as it needed it. The maxing out of RAM and unresponsiveness of the computer was just coincidental, I suppose.

If I come across a copy of Win8 or 10, I'll give it another shot, but I'm being told its my CPU.

it's "enough".  it's just gonna take a few extra secs to finish reading.  I had a system on F1 socket with 2 cores a while back it handled half a dozen drives just fine, read times were longer, that's all.

[Razerglass]

i realize theres big rollers and miners here i only have 5,4 TB and im not mining now its lags the prcessing a bit the blago miner soo i will stable after a new computer for that but the fork maight pass me by the 92000 blocks one

you could set process priority on your miner

[crowetic]

-BONUS ANN- -[ANN http://burst.ninja]-

Hello miner friends!


The ninja pool's bonus payout system has been setup and as a first run, I've dropped a 60k BURST BONUS , which will be distributed over the historic share pie.

Thank you for mining with us!

[catbref]

-BONUS ANN- -[ANN http://burst.ninja]-

Hello miner friends!


The ninja pool's bonus payout system has been setup and as a first run, I've dropped a 60k BURST BONUS , which will be distributed over the historic share pie.

Thank you for mining with us!

Uh, yeah, about that... it didn't work first time round (old config file) so I nicked the 60k Burst out of the bonus account and then resent it (with some extra by way of apology and thanks for people using my pool code).

[catbref]

Also, if we're giving out donations for PR, etc. in Burst then aren't these people going to convert the Burst to BTC/fiat ASAP and drive down the price?
Not sure what the alternative is...

[ltcnim]

-BONUS ANN- -[ANN http://burst.ninja]-

Hello miner friends!


The ninja pool's bonus payout system has been setup and as a first run, I've dropped a 60k BURST BONUS , which will be distributed over the historic share pie.

Thank you for mining with us!

Uh, yeah, about that... it didn't work first time round (old config file) so I nicked the 60k Burst out of the bonus account and then resent it (with some extra by way of apology and thanks for people using my pool code).

I can confirm the bonus, but it came from a different BURST address. However, I did receive two payouts from that adress. One just a few minutes ago, and one (smaller) around 4-5 h ago. If the first one was unintended, just tell me and I'll send it back.