Better reply now that I'm home.
Figures right after I catch up the payout queue a failsafe happens and puts it behind again. *sigh* I'll try to do another tonight. I like it cleaned up!
Anyhow, sorry for the confusion. I've been trying to make it so that the stats maintain most of their functionality regardless of the status of the reward system code. Seems I have a few kinks to work out on that front still.
I'm rebuilding the share log for the past half-day to make sure everything is correct. I don't foresee any issues, but, you never know. This is expected to take roughly 90-120 minutes, at which point the stats should automatically start updating again.
As always, all shares are accounted for. The pool will not accept shares if they can't be stored and tallied, so, regardless of the status of the stats pages, if the pool accepts your shares then all is well and you will be paid as you should be for those shares. Eligius is setup to be very redundant in this manner.
Thanks for mining!
-wk
Thanks for your hardwork and efforts wk,
For your information, your dev patch for Nov Jupiter is already almost as perfect as it can be. It's even better than any KnC firmwares they have churn out so far, and even better than your own dedicated KnC server. They should really hire you as their staff. Hehe!
Before applying this fix at stock KnC .99E firmware. I'm getting only 670GH/S hardware side, and coupled with 8-10% HW error, poolside hashrate always ended up around 600+ GH/S only.
Now with the same firmware, main pool (not KnC) but with your "temporary" fix, i get 690GH/S at hardware side, and although with the higher HW Reject of almost 2%, the HW Error itself is almost negligbile (~0.05%). Therefore with a total combination error of 2% (WU: 9530 stable), the pool side hash rate (12 hrs average) is amazingly stable at 675+ GH/S (690GH/S-2%) . What more can i ask for? Now, if only the rejects can be eliminated
http://s17.postimg.org/5gotykwi3/Untitled.jpgI have never even gotten anywhere close to 690GH/S hardware side at any other mining pool before. Most i'm getting is about 680GH/S (as shown in cgminer), and with the relatively same HW error of 1.5%, the poolside hashrate always ended up below 670GH/S no matter what i do.
I'm curious on what magic did you put into place to have the hardware running at 690GH/S when all other pools fails to do so? I'm pretty sure it's not a false indication because the pool side hashrate is reflecting the correct net hashrate after 2% deduction. I really don't think you can squeeze anything more out of this, can you? 2% HW is already considered low, unless you can bring it down further to 1% while keeping the 690GH/S as shown on cgminer
You are not obligated to provide a any fix for KnC and yet you did. Keep up the good job!