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

[yellowduck2]

i was gettin 500 per share with 30gb 1 week ago, or maybe is the dev trolling us

1 week ago might be possible but now it's not.

Its not possible to accumulate 9k coin without getting payout no matter how big the farm. Because once pool find block all shares will be paid and record reset to zero. That 9.65k payout is 1 single payout from pool. Not multiple payout.

U take sometime and obverse how the pool works u will understand what i am saying and know 9k coin is not possible in a single payout from pool. An account can accumulate multiple payout from pool to hit 9k but not in a single pool payout. The payout on pool is 2 stage. 1st stage payout can never hit 9k whereas 2nd stage payout is possible. The record shown on pool is showing 1st stage payout of 9.65k. The delay of payout u talk about is 2nd stage payout. 1st stage never get delay because it will be reset once a block is found. Once a block is found , stage 1 share will be calculated and final share of coins will move to stage 2 queuing for payout

[1714783950]

1714783950

[Amph]

i was gettin 500 per share with 30gb 1 week ago, or maybe is the dev trolling us

1 week ago might be possible but now it's not.

Its not possible to accumulate 9k coin without getting payout no matter how big the farm. Because once pool find block all shares will be paid and record reset to zero. That 9.65k payout is 1 single payout from pool. Not multiple payout.

U take sometime and obverse how the pool works u will understand what i am saying and know 9k coin is not possible in a single payout from pool. An account can accumulate multiple payout from pool to hit 9k but not in a single pool payout. The payout on pool is 2 stage. 1st stage payout can never hit 9k whereas 2nd stage payout is possible. The record shown on pool is showing 1st stage payout of 9.65k. The delay of payout u talk about is 2nd stage payout. 1st stage never get delay because it will be reset once a block is found. Once a block is found , stage 1 share will be calculated and find share of coins will move to stage 2 queuing for payout

so you are saying that someone is cheating?

[yellowduck2]

i was gettin 500 per share with 30gb 1 week ago, or maybe is the dev trolling us

1 week ago might be possible but now it's not.

Its not possible to accumulate 9k coin without getting payout no matter how big the farm. Because once pool find block all shares will be paid and record reset to zero. That 9.65k payout is 1 single payout from pool. Not multiple payout.

U take sometime and obverse how the pool works u will understand what i am saying and know 9k coin is not possible in a single payout from pool. An account can accumulate multiple payout from pool to hit 9k but not in a single pool payout. The payout on pool is 2 stage. 1st stage payout can never hit 9k whereas 2nd stage payout is possible. The record shown on pool is showing 1st stage payout of 9.65k. The delay of payout u talk about is 2nd stage payout. 1st stage never get delay because it will be reset once a block is found. Once a block is found , stage 1 share will be calculated and find share of coins will move to stage 2 queuing for payout

so you are saying that someone is cheating?

possible. I already reported this on pool thread. But this is the first time i saw it. And it was 1 time off. It never occur again.

But the "good news" is the payout i think is only for 1 full round. It will not affect other full round of shares. Every payout he get only affect 1 full round. It never occur again.

But if u see someone keep getting 9k payout for every full round , then we got a big problem

U can observe the payout on the bottom right side panel "Recent Payment". It rarely hit 2k. If u see something above 3k , click on the address it will direct u to block chain for investigation

[unsoindovo]

hum...
on http://burst-pool2.cryptoport.io/
today
from 11:57:44 to 16:35:05 just 301 burst with 12TB plot!!!
is not littel payment???

pool dev is trolling us???        

or it is correct

here https://bchain.info/BURST/tools/calculator with 12Tb i can read

Coins per day:   12947

[Amph]

well i'm checking every few hours if my payout are correct, if my payout will decrease for too long, i'll switch to solo

for now they seems good

and as long as mine are correct i don't care about others payout lol

[yellowduck2]

well i'm checking every few hours if my payout are correct, if my payout will decrease for too long, i'll switch to solo

for now they seems good

They are very good for me since it open yesterday. My payout was way better than pool 1 might be because i keep getting missing share on pool 1 due to error submitting or delay submitting or whatever error that keep showing on miner

Pool 2 is god send for me. Not a single error message on miner since i join.

[Blago]

He дo кoнцa пoнял пpo пpoвepкy пepвыx бaйтoв пocлe гeнepaции плoтcoв нa пpoцeccope и видeoкapтe. Moжeт ктo нибyдь пoяcнить ?

coздaй фaйл c пoмoщью пpoцeccopa 48712486872462871628746 1 1 1000 5
A пoтoм coздaй фaйл c тaкими жe xapaктepиcтикaми c пoмoщью гpaфичecкoй кapты и cpaвни вec oбoиx фaйлoв в пaпкax нaзнaчeния.Ecли вec в бaйтax coвпaдaeт тo вcё в шoкoлaдe

вec мoжeт и coвпacть, cмoтpeть нaдo coдepжимoe. в кoммaнднoй cтpoкe нaбиpaeшь  fc /b имяфaйлaЦпy имяфaйлaГпy     и oн тeбe пoкaжeт oтличия внyтpи фaйлoв, ecли нeт oтличий - тo вce нopм. фaйлы дoлжны быть c oдинaкoвыми пapaмeтpaми, пoлoжи иx в paзныe пaпки.

[m3ta]

and as long as mine are correct i don't care about others payout lol

That's the spirit.
If you get hit by a truck, "others" won't care, either.

[fivebells]

Messed around with the 2.0.1 plotter kernel a bit, and got it running a bit faster.

https://mega.co.nz/#!vsommLbQ!C9v0TshBm0JY8DMBC8DsM9wCtZvvGjsVDNl9wGr0DKU
Replace the kernel folder with the one provided.

This is about 35% slower on a Titan Black.

Edit:  Actually, I'm getting better performance if I tweak the parameters.  I'll discuss it more over on the forum.

[Amph]

and as long as mine are correct i don't care about others payout lol

That's the spirit.
If you get hit by a truck, "others" won't care, either.

in that case i won't care also lmao

[coinits]

and as long as mine are correct i don't care about others payout lol

That's the spirit.
If you get hit by a truck, "others" won't care, either.

in that case i won't care also lmao

Road Pizza en Francais LOL

[wacko]

The readme for gpuplotter 2.0.1 says:

Multiple graphic cards (preferred way)
--
In this mode, all the non-bound graphic cards can be used to generate plots without any timeout issue.
The typical <hashesNumber> parameter will be 8160.

Is it possible to use multiple gpus at once to build one plot, or is it only "one card per one plot" at the same time? Seems like it's required to specify gpu id in the command-line (after the platform id), so is there a way to specify 2 or 3 gpus there somehow?

[twig123]

The readme for gpuplotter 2.0.1 says:

Multiple graphic cards (preferred way)
--
In this mode, all the non-bound graphic cards can be used to generate plots without any timeout issue.
The typical <hashesNumber> parameter will be 8160.

Is it possible to use multiple gpus at once to build one plot, or is it only "one card per one plot" at the same time? Seems like it's required to specify gpu id in the command-line (after the platform id), so is there a way to specify 2 or 3 gpus there somehow?

One per plot. So, you'd have to start multiple plotters to use multiple GPUs

[twig123]

I guess I have a problem. I've been generating plots all night, currently got 170,000 nonces and still none of my shares have been valid and I have 0 mined balance.
I know that 170,000 isn't that much, but seriously - nothing? I guess I'm doing something wrong.


EDIT: Also, I always get the "error reading file message" - any idea what's wrong?

I said you that you are overlapping! Delete the plots that start from 17001 and begin a new plot that start from 600001..

This is wrong information... the 2nd number is the number of nonces to create, NOT the stopping nonce.
If starting nonce is 17000, and it is set to create 600000 nonces the next file would NOT start at nonce 600001. Doing so would cause an overlap of 17000 nonces.

Formula is {Starting_Nonce} + {Number_of_nonce_to_create} = {next starting nonce}

So, if the current file is plotted with 17000 600000, then the 2nd plot would be 617000 600000

[alphateam]

Block explorer down?

[alphateam]

and as long as mine are correct i don't care about others payout lol

That's the spirit.
If you get hit by a truck, "others" won't care, either.

in that case i won't care also lmao

Road Pizza en Francais LOL

you're french?

[wacko]

One per plot. So, you'd have to start multiple plotters to use multiple GPUs

Thanks. So does this mean that basically the only way to use multiple GPUs in one rig efficiently (= simultaneously) is to build plots on multiple HDDs at the same time with 1 gpu per 1 HDD? Although I suppose it's possible to divide 1 HDD into several partitions and fill each partition of the same disk simultaneously, assigning 1 gpu per partition? If that is possible, then we'll run into maximum disk write speed limit pretty quickly, cause ordinary HDDs won't like it when huge chunks of data are written to different partitions at the same time..

[Blago]

Messed around with the 2.0.1 plotter kernel a bit, and got it running a bit faster.

https://mega.co.nz/#!vsommLbQ!C9v0TshBm0JY8DMBC8DsM9wCtZvvGjsVDNl9wGr0DKU
Replace the kernel folder with the one provided.

This is about 35% slower on a Titan Black.

Giga 280x, parameters 0 8000 4000 128 4000
original: 11162,8 nonces/min
mod: 17777,8 nonces/min

[twig123]

One per plot. So, you'd have to start multiple plotters to use multiple GPUs

Thanks. So does this mean that basically the only way to use multiple GPUs in one rig efficiently (= simultaneously) is to build plots on multiple HDDs at the same time with 1 gpu per 1 HDD? Although I suppose it's possible to divide 1 HDD into several partitions and fill each partition of the same disk simultaneously, assigning 1 gpu per partition? If that is possible, then we'll run into maximum disk write speed limit pretty quickly, cause ordinary HDDs won't like it when huge chunks of data are written to different partitions at the same time..

I'm not sure of the throughput required for GPU Plotting, so I'm not sure if plotting to the same drive would cause slowdowns. Someone would need to test..
Also, by partitioning a drive, you are not doing yourself any favors. Sure the drive shows up as 2 drive letters... but it is still the same physical disk, so it will still be confined to the same max write speed as if it was a single partition.

[wacko]

Also, by partitioning a drive, you are not doing yourself any favors. Sure the drive shows up as 2 drive letters... but it is still the same physical disk, so it will still be confined to the same max write speed as if it was un-partitioned.

Well, that's exactly what I meant when saying "we'll run into maximum disk write speed limit pretty quickly", since the maximum write speed is for the whole drive, so when writing to multiple partitions simultaneously, you'll be limited by 'max_write_speed/number_of_partitions' at best. The more partitions you write at once, the bigger penalty you'll have. If we assume the average max write speed of around 100-150 MB/sec, then it'll be 50-75 MB/sec at most when writing to 2 partitions simultaneously. I'm using 7970 cards right now, and getting 15-16 k per minute, that's what, 60-65 MB/sec.. It might actually make sense to divide each drive in 2 partitions and use 1 GPU per partition simultaneously. Would be 1.5-2x times faster to fill one drive with 2 partitions and 2 gpus, rather than to use 1 gpu for plotting on 1 big partition.