On network delays 2.7.4 seems to not bleed shares to my backup pool. I am showing 600Mhahs on pool 0 with pool not providing work fast enough. Using a BFL single with 864 bitstream. Not throttling and no HW errors. If the pool it is on is able to handle the load then it will hit 860 and stay at greater then or equal to 859.
...
Just a small note about BFLs
The actual MH/s value is slightly affected by difficulty change.
The change is very small, but it is big enough to see in the screen display (and the API)
Firstly as everyone probably knows, you lose on average 1/2 a nonce range per LP.
With an LP average time of
10mins, on the
864MH/s bitstream:
Nonce range time is
~4.971 seconds so on average you lose (half that)
~2.4855 seconds per LP or ~2.4855 / 600 =
~0.414%So 864 - 0.414% = 864 -
3.58MH/s or a max expected average hash rate of
860.4MH/sHowever, if the difficulty is increasing - e.g. last difficulty increased
11.4% - that means you got the LP's 11.4% faster, on average, for the entire 2016 blocks (almost 2 weeks)
Thus the above
~0.414% increases to ~2.4855 / ~531.6 =
~0.468% which is
4.04MH/sSo the maximum average expected hash rate was actually
860.0MH/s for those 2016 blocks.
Now that's not much different, but it is enough to actually see the difference on the screen and in the API and also explain where that tiny 0.4 MH/s disappeared to
