Pages:
Author

Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 55. (Read 379087 times)

legendary
Activity: 1750
Merit: 1007
thanks again.
I was wondering if you can make the list of workers sorted?  I did not put all my workers in at one time and it is hard to distinguish between one rig and another.
btw, your interface for monitoring is what keeps me, not the 0% fee
txs
Jim

Worker stats are now in alphabetical order as they were before the DDoS.  Not included on the timeline is the ability to have a resettable share/stale counter rather than just round/total.  Reset stats should be back on the 14th.
legendary
Activity: 1876
Merit: 1000

thanks again.

I was wondering if you can make the list of workers sorted?  I did not put all my workers in at one time and it is hard to distinguish between one rig and another.

btw, your interface for monitoring is what keeps me, not the 0% fee

txs
Jim
legendary
Activity: 1750
Merit: 1007
It still seems to be getting an idle when the server manages to find a block, but it only lasts about 10-15 seconds based on monitoring my personal miners.

Any plans to fix that in the future? 10-15seconds is enough time to knock my miners into backup mode.
Also, 10-15 seconds of idle time is roughly 1% wasted for a 25min round, which adds up in the long run.

I can confirm the stale shares has been greatly improved, good work!


I just tweaked the load balancer (which is what caused the idles and disconnects), and when we found a block I only saw about 3 seconds idle time, from the pushpool instance that actually found the block.  This time it didn't kill off the LP connection/server connection, just a short idle spurt.  I'm working on finding out if its the LB or Pushpool that is causing the final small delay.  It may be pushpool hanging for a moment while it opens up SQL connections with the other servers to publish the new block.

Timeline for the rest of the week/weekend can be found at: http://www.btcguild.com/timeline.php
sr. member
Activity: 280
Merit: 250
Firstbits: 12pqwk
It still seems to be getting an idle when the server manages to find a block, but it only lasts about 10-15 seconds based on monitoring my personal miners.

Any plans to fix that in the future? 10-15seconds is enough time to knock my miners into backup mode.
Also, 10-15 seconds of idle time is roughly 1% wasted for a 25min round, which adds up in the long run.

I can confirm the stale shares has been greatly improved, good work!
legendary
Activity: 1876
Merit: 1000
Really nice work eleu.

Totals   5,955.69 MH/s   1009 (0)   0% on 1k shares Smiley

legendary
Activity: 1750
Merit: 1007
Stales are indeed GREATLY reduced (they're not gone, and I'm sure someone will come in complaining about 91.13% stales right after I go to bed).  The load balancer is now functioning far better on US West.  It still seems to be getting an idle when the server manages to find a block, but it only lasts about 10-15 seconds based on monitoring my personal miners.
newbie
Activity: 52
Merit: 0
Zero stales. It's great.
Eri
sr. member
Activity: 264
Merit: 250
my luck was in the positive thanks to last night but it seems all I'm getting now is errors on us/uswest. had a fratcion of my shares go through but that is way low, could have been bad luck combined with errors though. ive been getting these errors for hours.
full member
Activity: 134
Merit: 100
Well good news maybe.

I ended up having to restart my miners and surprisingly it ended up being ~roughly~ the same time as a round started.

My miners show

913.52 Mhash/sec - 886 Accepted - 5 Rejected = .564% Rejected

at the same +- minute BTCGuild shows: 896 (0)

I hope you're not counting stales so people stop bitching? How do I submit stales automatically lol;o)

But my apologies, this is supposed to be a kudos for low stales. So Kudos. lol sorry it sounds weak now.
member
Activity: 103
Merit: 10
All of my workers just got dropped again(They will be back after some minutes)
I don't know if it's because we just solved a block or something eles.

and pool hash dropped to 1600Gh from 2000Gh.
legendary
Activity: 1750
Merit: 1007
Just changed the pushpool configurations on US West.  Spoke with jine eariler, and there is some unknown bug in the Longpoll Keep-alive patch, which could very well be the culprit for a number of the problems today.

The next step if this doesn't improve stability is rolling back to pushpool and bitcoind stock code rather than the RPC keepalive/built in long polling versions.  Running out of items to cross off the list of trouble makers.



UPDATE:  ~50 minuets later.  497 shares on my phoenix miners (the "worst" for stales), 0 rejected.  0 idles.  0 long poll disconnects.  Looking promising.
legendary
Activity: 2072
Merit: 1001
connections problems to us.btcguild.com right now. maybe you are on the server tweaking things. unsure.
miners just getting disconnected, pause, then pick back up after a few seconds. idles. etc...
legendary
Activity: 1876
Merit: 1000
NEW BLOCK FOUND, pleaaaaase let it be valid!

#   Block Link   Date/Time   Duration   Shares   Validity   My Shares   Earned   Donated   Details
1566
Fetching   2011-07-12 19:40:35   2:30:09   4287311   119 until confirmed   1700   0.01982594   0.00000000   
View

if you donated 2.5% instead of 0.  then you wouldn't worry if it was valid or not.
legendary
Activity: 1750
Merit: 1007
Reporting my observation:

Everytime a block is found, 2 of my 3 workers automatically switch to my backup pool.
Which means there must be some idle or connection error when a round is finished.

You can also notice right before last block was found we're at 2000G+,
we dropped to 1700-1800G after finding a block.

The idles when we find a block are the root of the invalid problem.  I thought it was related to the calculation script, but I've profiled the time it takes to complete the different steps and the entire thing only runs for about 5 seconds, only about 1 second per server.

I'm thinking this is related to a bitcoind patch or the long poll keepalive patch.
newbie
Activity: 46
Merit: 0
Looks like the block is good, so far anyway.
member
Activity: 103
Merit: 10
Reporting my observation:

Everytime a block is found, 2 of my 3 workers automatically switch to my backup pool.
Which means there must be some idle or connection error when a round is finished.

You can also notice right before last block was found we're at 2000G+,
we dropped to 1700-1800G after finding a block.
newbie
Activity: 46
Merit: 0
NEW BLOCK FOUND, pleaaaaase let it be valid!

#   Block Link   Date/Time   Duration   Shares   Validity   My Shares   Earned   Donated   Details
1566
Fetching   2011-07-12 19:40:35   2:30:09   4287311   119 until confirmed   1700   0.01982594   0.00000000   
View
legendary
Activity: 1750
Merit: 1007
Thanks for all the hard work  Smiley

In order for you to do testing and track down the problem I think we need to find a block once every 5 minutes for the next hour. Think that should give you some good testing data  Cheesy


Unless it's broken, in which case that means I'd be losing about $200 every 5 minutes on invalid payouts...
member
Activity: 84
Merit: 10
I need an new box...
Thanks for all the hard work  Smiley

In order for you to do testing and track down the problem I think we need to find a block once every 5 minutes for the next hour. Think that should give you some good testing data  Cheesy
legendary
Activity: 1750
Merit: 1007
I ran a small test run (added a 5th pool to the load balancer for about 3 minutes) using testnet.  The problem is either fixed, or NOT directly related to the publishing of new blocks.  Won't be able to verify until we find a block on US West.
Pages:
Jump to: