Author

Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 597. (Read 4382755 times)

sr. member
Activity: 308
Merit: 250
Double your Personal Bitcoin Funds.
I've joined with single 7850 GPU and making 0.01 BTC a day which isn't bad. There were two minor incidents that I'd like an answer to.

First, yesterday I heard my GPU cranking really loud and upon inspection I was getting several hundred stale (connections?) in GUIMiner. At this time my account showed 0 hash rate. So I restarted my miner and everything came back to normal. I'd like to understand what happened there and what I can do to avoid it or possibly burning out my GPU.

Second, today everything was humming along and at the end of my work day I checked my account and it sowed last share 7 hours ago. I don't think I had made any contribution during this time. However my GUIMiner was clicking just normal showing 352 MH/S - In statistics, I have no shares from 19195 to 19199 while GUIMiner seem to be running normal. So I'd also like to find out what happened here?

I'm getting some USB ASIC chips on Monday and plan on changing over to BFGMiner. Is this the right thing to do with slush's pool?

Appreciate any input and keep up the good work.
hero member
Activity: 574
Merit: 500
I'm pretty new to Bitcoin mining and using three Satoshi Sticks (USB ASICs). cgminer indicates an average hash rate of 325 Mh/s per AMU. I've been connected to Slush's pool for a few hours, but on the "My accounts" page the "Mhash/s" stats say

285.69 Mh/s

with this number slowly increasing on page refreshes.

Questions:
- Why is this number significantly lower than 3 x 325 Mh/s?
- Will it keep increasing over time until it reaches the real rate, which cgminer indicates on my local machine?
- Why is this so?

Thanks for helping a Bitcoin mining newbie with this. :-)

--
Ralf | 1Bn35qkUS4X51hjszLzhVMHcmFb2GQXLEZ

This is all good ralf, the average is over the last ten rounds and when you check tomorrow, you should see similar slush rates to cgminer.

The only (minor) thing that I would say is that you should expect 333 MH/s per device - the fact you are only getting on 325 is not devastating but does indicate the miners are not getting enough power (amperage).

If you have them plugged into a cheap usb hub - try plugging them direct into any spare PC slots...

Welcome btw
legendary
Activity: 1778
Merit: 1008
I'm pretty new to Bitcoin mining and using three Satoshi Sticks (USB ASICs). cgminer indicates an average hash rate of 325 Mh/s per AMU. I've been connected to Slush's pool for a few hours, but on the "My accounts" page the "Mhash/s" stats say

285.69 Mh/s

with this number slowly increasing on page refreshes.

Questions:
- Why is this number significantly lower than 3 x 325 Mh/s?
- Will it keep increasing over time until it reaches the real rate, which cgminer indicates on my local machine?
- Why is this so?

Thanks for helping a Bitcoin mining newbie with this. :-)

--
Ralf | 1Bn35qkUS4X51hjszLzhVMHcmFb2GQXLEZ

it's determining hashrate via sucessfully submitted shares over a given time, i think ten minutes. thus, as you submit more shares, the relative speed increases. yes, it will continue to do so until it reflects the real rate.
newbie
Activity: 4
Merit: 0
I'm pretty new to Bitcoin mining and using three Satoshi Sticks (USB ASICs). cgminer indicates an average hash rate of 325 Mh/s per AMU. I've been connected to Slush's pool for a few hours, but on the "My accounts" page the "Mhash/s" stats say

285.69 Mh/s

with this number slowly increasing on page refreshes.

Questions:
- Why is this number significantly lower than 3 x 325 Mh/s?
- Will it keep increasing over time until it reaches the real rate, which cgminer indicates on my local machine?
- Why is this so?

Thanks for helping a Bitcoin mining newbie with this. :-)

--
Ralf | 1Bn35qkUS4X51hjszLzhVMHcmFb2GQXLEZ
hero member
Activity: 569
Merit: 500
19195   2013-07-20 14:28:49   0:05:05   8794745   9542   0.01586825   247569   25.07941640    96 confirmations left
19194   2013-07-20 14:23:44   2:02:34   39788670   37043   0.02297916   247567   25.18610000    94 confirmations left

Now #19194 is correct but #19195 is wrong again

9542 / 8794745 * 25.079 = 0.0272

mines wrong as it should be over 5000 shares not 2136

19194   2013-07-20 14:23:44   2:02:34   39788670   2136   0.00132505

all my miners connecting to 95.211.52.40 were not showing shares on the website so I changed them to 54.215.3.101


now 2 miners connecting to .101 are showing not connected for x minutes the X is a random number each reload.
So that says a backend server is not caught up with the others and since all my miners are going to .101 I have to assume he enabled some round robin back end and still 1 server isnt behaving.
hero member
Activity: 574
Merit: 500
19195   2013-07-20 14:28:49   0:05:05   8794745   9542   0.02666612   247569   25.07941640    93 confirmations left

Corrected. The formula should be

9542 / 8794745 * 25.079 * 0.98 = 0.0266

But what is the reason of these calculation errors? Manual processing? Pool software should handle this kind of calculation with 100% accuracy.

My best guess is some kind of connectivity issue between the back end pool servers when the shares for a round are being calculated/shared out - slush has addressed it several times and I believe he has made code changes - not only to try and stop it happening - but also to alert him when it does happen - all conjecture of course. Only one man truly knows and like a poster said earlier - he only lurks here now rather than post here. To be honest I don't blame him either - if it's something really important he can use his home page. As soon as he raises his head here all you see is:

1) Hey slush what about namecoins
2) Hey slush my calculation for block xxx is wrong, I only got 0.0000001 BTC and is should have been 0.0000002 - I'm using a 6 core CPU btw...
3) PPS is better than the slush calculation
4) PPLNS is better than the slush calculation
5) What is the slush calculation
6) ad infinitum
hero member
Activity: 569
Merit: 500
19195   2013-07-20 14:28:49   0:05:05   8794745   9542   0.01586825   247569   25.07941640    96 confirmations left
19194   2013-07-20 14:23:44   2:02:34   39788670   37043   0.02297916   247567   25.18610000    94 confirmations left

Now #19194 is correct but #19195 is wrong again

9542 / 8794745 * 25.079 = 0.0272

mines wrong as it should be over 5000 shares not 2136

19194   2013-07-20 14:23:44   2:02:34   39788670   2136   0.00132505

all my miners connecting to 95.211.52.40 were not showing shares on the website so I changed them to 54.215.3.101
donator
Activity: 229
Merit: 106
19195   2013-07-20 14:28:49   0:05:05   8794745   9542   0.02666612   247569   25.07941640    93 confirmations left

Corrected. The formula should be

9542 / 8794745 * 25.079 * 0.98 = 0.0266

But what is the reason of these calculation errors? Manual processing? Pool software should handle this kind of calculation with 100% accuracy.
hero member
Activity: 569
Merit: 500
19195   2013-07-20 14:28:49   0:05:05   8794745   9542   0.01586825   247569   25.07941640    96 confirmations left
19194   2013-07-20 14:23:44   2:02:34   39788670   37043   0.02297916   247567   25.18610000    94 confirmations left

Now #19194 is correct but #19195 is wrong again

9542 / 8794745 * 25.079 = 0.0272

mines wrong as it should be over 5000 shares not 2136

19194   2013-07-20 14:23:44   2:02:34   39788670   2136   0.00132505
hero member
Activity: 569
Merit: 500
I have 39 workers running -- 21 of them are running okay and 18 of them are having connection problems.

Very odd... also my "Estimated Reward" for the current block in process is about 75x higher than normal.

1 or 2 of his servers isnt communicated with the main one.  I changed my ip's of the miners that were showing shares on the website to a different server and now they are showing shares again
donator
Activity: 229
Merit: 106
19195   2013-07-20 14:28:49   0:05:05   8794745   9542   0.01586825   247569   25.07941640    96 confirmations left
19194   2013-07-20 14:23:44   2:02:34   39788670   37043   0.02297916   247567   25.18610000    94 confirmations left

Now #19194 is correct but #19195 is wrong again

9542 / 8794745 * 25.079 = 0.0272
hero member
Activity: 574
Merit: 500
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
Seems like Slush is reading the forum but stays in "radio silence"  Shocked, rounds were re-calculated:

Code:
19195	2013-07-20 14:28:49	0:05:05	8794745		27264	0.04342803	247569	25.07941640	 96 confirmaciones pendientes
19194 2013-07-20 14:23:44 2:02:34 39788670 127616 0.07916491 247567 25.18610000 94 confirmaciones pendientes
19193 2013-07-20 12:21:10 1:19:38 13616177 40802 0.07386617 247548 25.15320000 75 confirmaciones pendientes
19192 2013-07-20 11:01:32 1:56:36 38748497 115968 0.07346108 247539 25.11490000 66 confirmaciones pendientes
19191 2013-07-20 09:04:56 1:23:38 27791450 78912 0.07612334 247522 25.16930256 49 confirmaciones pendientes
19190 2013-07-20 07:41:18 5:51:17 116255011 350144 0.08462781 247506 26.57599786 33 confirmaciones pendientes
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
...

[EDIT] for the long term slush miner - it all evens out

Negative  Undecided
hero member
Activity: 574
Merit: 500
Should I assume that block is Invalid ?

If it gets 100 confirmations then it's yours - slush spots about 95% of these and fixes them but people have been known to benefit (or lose) from these block mis-calculations - the best I ever got was around 8 times normal payout for a block that went to 100 confirmations - but I've had several where I got next to nothing and the 100 confirmations passed - this time I'm down - but for you it's all good unless slush sees it Wink

[EDIT] for the long term slush miner - it all evens out
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
Same thing here...

Code:
19194	2013-07-20 14:23:44	2:02:34	39788670	127616	0.00132161	247567	25.18610000	 95 confirmaciones pendientes
19193 2013-07-20 12:21:10 1:19:38 13616177 40802 0.07386617 247548 25.15320000 76 confirmaciones pendientes
19192 2013-07-20 11:01:32 1:56:36 38748497 115968 0.07346108 247539 25.11490000 67 confirmaciones pendientes
19191 2013-07-20 09:04:56 1:23:38 27791450 78912 0.07612334 247522 25.16930256 50 confirmaciones pendientes

If this keeps going the same way I'm out. Btw, Slush I know you're a busy person, me too, but don't forget to attend your pool and answer questions we ask, you're living on mining revenues. Your payout scheme is pulling results out of it's arse!
donator
Activity: 229
Merit: 106
19194   2013-07-20 14:23:44   2:02:34   39788670   37043   0.00043301   247567   25.18610000    95 confirmations left
19193   2013-07-20 12:21:10   1:19:38   13616177   5916           0.01071005   247548   25.15320000    76 confirmations left
19192   2013-07-20 11:01:32   1:56:36   38748497   38910   0.02470141   247539   25.11490000    67 confirmations left

Something is wrong with the last two block reward calculation. #19192 is normal, #19193 may be normal because of pool connection issue but #19194 is definitely wrong
hero member
Activity: 714
Merit: 512
I have 39 workers running -- 21 of them are running okay and 18 of them are having connection problems.

Very odd... also my "Estimated Reward" for the current block in process is about 75x higher than normal.



Should I assume that block is Invalid ?
hero member
Activity: 714
Merit: 512
Block changed and those 18 stayed down -- pretty odd combination as well... as they are spread over 3 locations and some workers on the same system are going and some are not. Suppose I'll have to go check on them all today.
hero member
Activity: 714
Merit: 512
I have 39 workers running -- 21 of them are running okay and 18 of them are having connection problems.

Very odd... also my "Estimated Reward" for the current block in process is about 75x higher than normal.
Jump to: