Bitcoin Forum
October 17, 2018, 11:15:50 AM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 [210] 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 ... 1145 »
  Print  
Author Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool  (Read 4342097 times)
Bigpiggy01
Hero Member
*****
Offline Offline

Activity: 834
Merit: 502



View Profile
October 27, 2011, 01:11:24 PM
 #4181

It looks like something is up.

My miners are all running properly though, so I suspect that it's Slush poking around with stats etc.

1539774950
Hero Member
*
Offline Offline

Posts: 1539774950

View Profile Personal Message (Offline)

Ignore
1539774950
Reply with quote  #2

1539774950
Report to moderator
1539774950
Hero Member
*
Offline Offline

Posts: 1539774950

View Profile Personal Message (Offline)

Ignore
1539774950
Reply with quote  #2

1539774950
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1539774950
Hero Member
*
Offline Offline

Posts: 1539774950

View Profile Personal Message (Offline)

Ignore
1539774950
Reply with quote  #2

1539774950
Report to moderator
1539774950
Hero Member
*
Offline Offline

Posts: 1539774950

View Profile Personal Message (Offline)

Ignore
1539774950
Reply with quote  #2

1539774950
Report to moderator
1539774950
Hero Member
*
Offline Offline

Posts: 1539774950

View Profile Personal Message (Offline)

Ignore
1539774950
Reply with quote  #2

1539774950
Report to moderator
slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 27, 2011, 01:14:41 PM
 #4182

Everything seems to be ok. It's "only" 9.5mil shares, so nothing impossible. For example, deepbit had 10+ mil shares in one round today, too.

Bigpiggy01
Hero Member
*****
Offline Offline

Activity: 834
Merit: 502



View Profile
October 27, 2011, 01:17:16 PM
 #4183

Estimated rewards etc seem totally off though atm  Wink

slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 27, 2011, 01:31:59 PM
 #4184

Estimated rewards etc seem totally off though atm  Wink

OK, it's only >estimated< reward; it's calculated from slightly outdated info (becuase of caching). I'll watch how rewards from this block will be finally distributed and if there will be something weird, I'll fix it. Thanks for pointing me to that.

RobertRibbeck
Full Member
***
Offline Offline

Activity: 221
Merit: 100


View Profile
October 27, 2011, 01:39:56 PM
 #4185

I really do not understand your scoring system.

30 seconds on google would explain the scoring system and all the other payout systems

https://en.bitcoin.it/wiki/Comparison_of_mining_pools

Score - Score based system: a proportional reward, but weighed by time submitted. Each submitted share is worth more in the function of time t since start of current round. For each share score is updated by: score += exp(t/C). This makes later shares worth much more than earlier shares, thus the miner's score quickly diminishes when they stop mining on the pool. Rewards are calculated proportionally to scores (and not to shares). (at slush's pool C=300 seconds, and every hour scores are normalized)


so when you see it drop back to 200 or whatever its because the scores were normalized...

With current pool hash rate Early shares submitted by a pool hopper will decline very quickly
every increase in total hash rate of the pool increases that rate of decline
The score system esentially makes what you submited at the beginning of a round worthless
even if you mine for the whole round

Please "Clear your browser cookies" then use http://bitcoinpyramid.com/r/3360 to Join BitCoin Pyramid
  use my referral & I'll refund a % of your first deposit back to your account
  Deposit .5 BTC or more and I'll give back 50% of what I receive

First Deposit of 1 BTC will get 75% of what I get back
digital
Hero Member
*****
Offline Offline

Activity: 490
Merit: 500


View Profile
October 27, 2011, 02:22:43 PM
 #4186

Hello everybody,

Is the pool ok?
As for me the current 9+ hour block looks a bit unlucky.
And the previous 4 hour too.

Yeah, im sure it's just unlucky.  I've seen 12+ hour blocks in the recent past (not counting the 1 1/2 day block from when the pool was ddos'ed).

Didn't happen as often when the pool was up around 2000 ghash, but now that its around 1200/1300 there is a lot more variance.

If I help you out: 17QatvSdciyv2zsdAbphDEUzST1S6x46c3
References (bitcointalk.org/index.php?topic=): 50051.20  50051.100  53668.0  53788.0  53571.0  53571.0  52212.0  50729.0  114804.0  115468  78106  69061  58572  54747
DutchBrat
Hero Member
*****
Offline Offline

Activity: 868
Merit: 1000


View Profile
October 28, 2011, 06:51:58 AM
 #4187

Most of my miners are getting:

Pool not responding errors

Are we being attacked again Huh
naypalm
Legendary
*
Offline Offline

Activity: 1263
Merit: 1003


coins coins coins!


View Profile WWW
October 28, 2011, 06:59:36 AM
 #4188

Looks alright on my end  Undecided

slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 29, 2011, 11:16:20 AM
 #4189

This weekend (29-30. October) I'm migrating pool from London (linode.com) to France (ovh.com). Although I believe everything will be fine, there will be at least one outage during database migration (probably something around 30 minutes).

kislam
Member
**
Offline Offline

Activity: 74
Merit: 10


View Profile
October 29, 2011, 03:11:11 PM
 #4190

Question for Slush:

In describing the logic/calculation of the score-based system, you mentioned this:

====
Matematically said, for every submitted share, pool perform

Code:
score = score + exp(round_time/C)

round_time is count of seconds between "now" and time when round started, C is magic constant which define how fast old shares lose their value. All following calculations are using C=300, but it may be changed in the future to provide the best cheatproof/usability ratio.

And on the end of round, system calculate rewards using formula

Code:
reward = user score / total score * 50
====

Is it really done for EVERY submitted share for EVERY user? that's a lot of calculations, no? or is there some other interval used to calculate the scores? maybe the scores are calculated at the end of each round?

please enlighten....

1PMHA7hyqqbcCbjMfwvKT4xEZ81EYasJze
slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 29, 2011, 03:23:00 PM
 #4191

score = score + exp(round_time/C)

This is done for every submitted share immediately.

Quote
reward = user score / total score * 50

This is done on the end of round.

Quote
Is it really done for EVERY submitted share for EVERY user?

Yes, why not? It's one exponent function per share. With current multigigahertz machines it really isn't an issue :-).

kislam
Member
**
Offline Offline

Activity: 74
Merit: 10


View Profile
October 29, 2011, 03:29:25 PM
 #4192

score = score + exp(round_time/C)

This is done for every submitted share immediately.

Quote
reward = user score / total score * 50

This is done on the end of round.

Quote
Is it really done for EVERY submitted share for EVERY user?

Yes, why not? It's one exponent function per share. With current multigigahertz machines it really isn't an issue :-).

It's one exponent function per share PER USER. if you have 200 users you are doing this calculation 200 times for each share? then adding the new score to the cumulative score for each user and storing that in memory? for all the millions of shares?

not that it would be difficult for the modern pc, but my question is if it is done on an ongoing basis, then why does it take about 10 minutes to publish the rewards after each round?

BTW, thx for the lightning fast response Smiley

1PMHA7hyqqbcCbjMfwvKT4xEZ81EYasJze
kislam
Member
**
Offline Offline

Activity: 74
Merit: 10


View Profile
October 29, 2011, 03:32:07 PM
 #4193

score = score + exp(round_time/C)

This is done for every submitted share immediately.

Quote
reward = user score / total score * 50

This is done on the end of round.

Quote
Is it really done for EVERY submitted share for EVERY user?

Yes, why not? It's one exponent function per share. With current multigigahertz machines it really isn't an issue :-).

It's one exponent function per share PER USER. if you have 200 users you are doing this calculation 200 times for each share? then adding the new score to the cumulative score for each user and storing that in memory? for all the millions of shares?

not that it would be difficult for the modern pc, but my question is if it is done on an ongoing basis, then why does it take about 10 minutes to publish the rewards after each round?

BTW, thx for the lightning fast response Smiley

sorry, just realized my mistake, a share is not submitted by multiple users and still be valid. so no need to multiply by number of users...

1PMHA7hyqqbcCbjMfwvKT4xEZ81EYasJze
worldinacoin
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500



View Profile
October 29, 2011, 03:33:17 PM
 #4194

It is great mining for NMC in Slush's Pool but my luck is real bad on BTC for quite sometime.   
slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 29, 2011, 03:42:37 PM
 #4195

It is great mining for NMC in Slush's Pool but my luck is real bad on BTC for quite sometime.   

Is your expected round reward significantly lower than it should be? For eliminate effect of score based system, you can take last 50 round rewards and recalculate it with proportional method (your hashrate against pool hashrate, which is pretty constant around 1170 for last few days).

If this fits, then it's pool luck (well, we performed pretty bad last few days). If it don't fit, then we need to investigate more. Usually it's because of some connection troubles, rejected shares or crippled miner software or cards. Actually I don't have a reason to think there's some flaw in pool code, I didn't touch important stuff for many weeks and merged mining cannot affect this.

DutchBrat
Hero Member
*****
Offline Offline

Activity: 868
Merit: 1000


View Profile
October 29, 2011, 03:43:19 PM
 #4196

It's a good thing luck evens out in infinity,

so give it a few more years and we will be alright  Wink

Brat
slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 29, 2011, 03:44:23 PM
 #4197

It's one exponent function per share PER USER. if you have 200 users you are doing this calculation 200 times for each share? then adding the new score to the cumulative score for each user and storing that in memory? for all the millions of shares?

As you already realized, score is calculated only for one share submit, not for submit*users :-).

DutchBrat
Hero Member
*****
Offline Offline

Activity: 868
Merit: 1000


View Profile
October 29, 2011, 05:05:03 PM
 #4198

I am experiencing a lot of:

'Pool not providing work fast enough'
'Pool not responding'

Errors

Is this because of the switch to a French provider ?
slush
Legendary
*
Offline Offline

Activity: 1372
Merit: 1020



View Profile WWW
October 29, 2011, 05:08:31 PM
 #4199

Is this because of the switch to a French provider ?

Not yet.

It's cgminer, right? Whats your ping to api.bitcoin.cz?

Edit: I'm monitoring pool response times once they took longer than 2 seconds; it happen time to time and it's an idicator that something is broken. But now there's no problem with response times, they're far under this threshold (actually most loaded pool backend has server load 0.15, which is excellent), so I don't see any reason why you should see this error.

Edit2: Also is there any ping packetloss?

DutchBrat
Hero Member
*****
Offline Offline

Activity: 868
Merit: 1000


View Profile
October 29, 2011, 05:12:42 PM
 #4200

Pinging api.bitcoin.cz [178.79.183.97] with 32 bytes of data:

Reply from 178.79.183.97: bytes=32 time=6ms TTL=54
Reply from 178.79.183.97: bytes=32 time=6ms TTL=54
Reply from 178.79.183.97: bytes=32 time=6ms TTL=54
Reply from 178.79.183.97: bytes=32 time=6ms TTL=54

Looking good to me
Pages: « 1 ... 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 [210] 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 ... 1145 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!