Topic: [250GH/s] BitClockers.com Merged/No Invalids/Pure PPS/DDoS-Resistant/Live Stats - page 16. (Read 75796 times)
July 14, 2011, 05:00:19 PM
Hash rate is a 15 min average not an average of the entire round
July 14, 2011, 02:14:29 PM
Burp: Try pool2.bitclockers.com or pool3.bitclockers.com on your miners. Might be closer to you.
Thanks, pool2 and pool3 have no such issues for me
I'm sure though this isn't a distance-latency issue, as the ICMP ping is low for all pools.PS: Are you sure the pool hashrate display is correct?
Live Statistics
Hash Rate: 245.60 Gh/s
Active Workers: 633
Shares This Round: 198,229
Current Round Duration: 1 hours 11 minutes
198229*2^32 / (71*60) / 10^9 = 199.856120215677
July 14, 2011, 02:12:35 PM
Burp: Try pool2.bitclockers.com or pool3.bitclockers.com on your miners. Might be closer to you.
July 14, 2011, 02:10:17 PM
Bitclockers is basically unusable for me. I'm getting very high variances on the pool connectivity (which happens nowhere else).. changes from 1/2 to 10 seconds.
ICMP ping is at stable 220ms, so this is defenitely a problem on your side
Code:
% httping -h pool.bitclockers.com -p 8332 [21:08:03]
PING pool.bitclockers.com:8332 (http://pool.bitclockers.com:8332/):
connected to pool.bitclockers.com:8332, seq=0 time=969.53 ms
connected to pool.bitclockers.com:8332, seq=1 time=905.77 ms
connected to pool.bitclockers.com:8332, seq=2 time=1097.10 ms
connected to pool.bitclockers.com:8332, seq=3 time=773.19 ms
connected to pool.bitclockers.com:8332, seq=4 time=634.67 ms
connected to pool.bitclockers.com:8332, seq=5 time=926.27 ms
connected to pool.bitclockers.com:8332, seq=6 time=786.47 ms
connected to pool.bitclockers.com:8332, seq=7 time=578.01 ms
connected to pool.bitclockers.com:8332, seq=8 time=4005.03 ms
connected to pool.bitclockers.com:8332, seq=9 time=931.53 ms
connected to pool.bitclockers.com:8332, seq=10 time=1148.74 ms
connected to pool.bitclockers.com:8332, seq=11 time=3763.78 ms
connected to pool.bitclockers.com:8332, seq=12 time=885.18 ms
connected to pool.bitclockers.com:8332, seq=13 time=1049.96 ms
connected to pool.bitclockers.com:8332, seq=14 time=983.03 ms
connected to pool.bitclockers.com:8332, seq=15 time=874.24 ms
connected to pool.bitclockers.com:8332, seq=16 time=3808.05 ms
connected to pool.bitclockers.com:8332, seq=17 time=9919.28 ms
connected to pool.bitclockers.com:8332, seq=18 time=978.05 ms
connected to pool.bitclockers.com:8332, seq=19 time=971.40 ms
connected to pool.bitclockers.com:8332, seq=20 time=803.95 ms
connected to pool.bitclockers.com:8332, seq=21 time=902.08 ms
connected to pool.bitclockers.com:8332, seq=22 time=3945.37 ms
connected to pool.bitclockers.com:8332, seq=23 time=981.57 ms
PING pool.bitclockers.com:8332 (http://pool.bitclockers.com:8332/):
connected to pool.bitclockers.com:8332, seq=0 time=969.53 ms
connected to pool.bitclockers.com:8332, seq=1 time=905.77 ms
connected to pool.bitclockers.com:8332, seq=2 time=1097.10 ms
connected to pool.bitclockers.com:8332, seq=3 time=773.19 ms
connected to pool.bitclockers.com:8332, seq=4 time=634.67 ms
connected to pool.bitclockers.com:8332, seq=5 time=926.27 ms
connected to pool.bitclockers.com:8332, seq=6 time=786.47 ms
connected to pool.bitclockers.com:8332, seq=7 time=578.01 ms
connected to pool.bitclockers.com:8332, seq=8 time=4005.03 ms
connected to pool.bitclockers.com:8332, seq=9 time=931.53 ms
connected to pool.bitclockers.com:8332, seq=10 time=1148.74 ms
connected to pool.bitclockers.com:8332, seq=11 time=3763.78 ms
connected to pool.bitclockers.com:8332, seq=12 time=885.18 ms
connected to pool.bitclockers.com:8332, seq=13 time=1049.96 ms
connected to pool.bitclockers.com:8332, seq=14 time=983.03 ms
connected to pool.bitclockers.com:8332, seq=15 time=874.24 ms
connected to pool.bitclockers.com:8332, seq=16 time=3808.05 ms
connected to pool.bitclockers.com:8332, seq=17 time=9919.28 ms
connected to pool.bitclockers.com:8332, seq=18 time=978.05 ms
connected to pool.bitclockers.com:8332, seq=19 time=971.40 ms
connected to pool.bitclockers.com:8332, seq=20 time=803.95 ms
connected to pool.bitclockers.com:8332, seq=21 time=902.08 ms
connected to pool.bitclockers.com:8332, seq=22 time=3945.37 ms
connected to pool.bitclockers.com:8332, seq=23 time=981.57 ms
ICMP ping is at stable 220ms, so this is defenitely a problem on your side
July 14, 2011, 01:55:16 PM
Block was so fast it didn't hit the update balance trigger. Was caught and automatically fixed within a few hours. You are good to go
As far as terrible luck, donno what to say. I think the current graph says it all:
Current block average is 73,000 shares under difficulty (1,563,027) for a luck of +4.67%
July 14, 2011, 07:13:43 AM
Are there still block payout issues on BitClockers?
http://bitclockers.com/blockhistory/block/48
Most of the workers did not get paid.
And I have a total of 6607 shares for total earnings of ~0.16766873. That's a really bad rate per share. I know the pool isn't PPS, but are we that unlucky? At average luck we should be getting close to 0.00003198/share but I'm only getting 0.00002538/share.
Seems like terrible luck.
A total of 22774221 shares for the last 13 blocks. That's 0.00002854/share. Or 1751863 shares/block. And 48428226 for the last 25 blocks. That's even worse at 1937129 shares/block.
http://bitclockers.com/blockhistory/block/48
Most of the workers did not get paid.
And I have a total of 6607 shares for total earnings of ~0.16766873. That's a really bad rate per share. I know the pool isn't PPS, but are we that unlucky? At average luck we should be getting close to 0.00003198/share but I'm only getting 0.00002538/share.
Seems like terrible luck.
A total of 22774221 shares for the last 13 blocks. That's 0.00002854/share. Or 1751863 shares/block. And 48428226 for the last 25 blocks. That's even worse at 1937129 shares/block.
July 13, 2011, 10:04:05 PM
I'm workin' hard for that 6950 
July 13, 2011, 02:16:24 PM
Hey Back, are you guys having to pay for these Radeon's out of pocket or are you getting them through a sponsor or something? I'd hate to think you guys are stuck footing the bill and fees aren't covering everything...
I ordered the card from newegg and donated it to the pool. I really want to see the pool grow and am trying to attract some more attention to bitclockers.
July 12, 2011, 04:33:27 PM
I just watched him order it
July 12, 2011, 03:30:03 PM
Ah, nice! Thanks V2!
July 12, 2011, 02:31:11 PM
From what I understand, V2 is donating the cards for the giveaways.
July 12, 2011, 07:22:04 AM
Hey Back, are you guys having to pay for these Radeon's out of pocket or are you getting them through a sponsor or something? I'd hate to think you guys are stuck footing the bill and fees aren't covering everything...
July 12, 2011, 05:36:38 AM
Hey Backburn, is Pool3 in the Czech Republic running nicely?
I wasn't aware there was more options to connect to... It would be nice to connect to something closer (I'm in Germany)
I wasn't aware there was more options to connect to... It would be nice to connect to something closer (I'm in Germany)
July 11, 2011, 02:16:16 PM
Daaayyyyyuuuummm!
Lot's of blocks poppin' out these last few days
Lot's of blocks poppin' out these last few days
July 11, 2011, 12:35:52 PM
Thanks for the hard work and for keeping us informed, much appreciated.
July 10, 2011, 04:50:15 PM
Yey for breaking 200Ghash!
On a less pleasant note: Our webservers have been under a DDoS attack for several days, fortunately our content delivery network banned their botnet zombies as fast as they threw them at us.The jerks finally gave up on trying to kill our website and have resorted to flooding our pushpool servers with bad login requests and simple syn flooding.
I spent the night writing a work around; everything should be fine now and idles should no longer be reported in your clients.
On a less pleasant note: Our webservers have been under a DDoS attack for several days, fortunately our content delivery network banned their botnet zombies as fast as they threw them at us.The jerks finally gave up on trying to kill our website and have resorted to flooding our pushpool servers with bad login requests and simple syn flooding.
I spent the night writing a work around; everything should be fine now and idles should no longer be reported in your clients.
July 09, 2011, 04:09:29 PM
214 GHash/s and nearly 820 Workers!!!! http://bitclockers.com/statistics
July 08, 2011, 11:07:49 AM
Well hello 200GHash/s i didn't expect to see you waking up this morning!
July 08, 2011, 02:05:46 AM
Hmmm I wonder where those people came from?
Go Bitclockers (:
Go Bitclockers (:
July 07, 2011, 11:52:38 PM
Huge jump in hashing power and user base today! glad to see some new faces
Jump to: