Author

Topic: higher calculated hashrate than reported hashrate.. error or luck? (Read 147 times)

hero member
Activity: 687
Merit: 511
Luck typically refers to pools finding blocks faster than projected times - so I don't know what I would necessarily call speed discrepancy 'luck' - the more accurate terms (and what I typically use) is variance.

You definitely will find variance in hash rate, and it could be more than 24 hours - because at some point you'll run into 24 hours of +10% hash and you'll be patting yourself on the back for your masterful tuning of the rig.  Wink  The nature of mining is that most PoW solves are probabilistic in nature, so your estimated hash rate will become more accurate the larger the sample time.  For instance, your variance might be 10% for 1 minute, 5% for one day, and 1% for one month.

Beyond the general affect of variance, you might also just confirm that the card temps are running as expected - so if they were running too hot and being throttled you'll be getting less.

Finally, when you're looking at multiple rigs, some pools wrap in stale shares and other hash-affecting things into your overall hash rate, so it will appear lower - although once again, if this number (like stale shares) is overly high, you probably need to look into things and will cause less than expected hash performance.

Hope that helps.  Wink
newbie
Activity: 60
Merit: 0
As title says, my reported hashrate, the one I see on claymore, is about 755mh/s.
My calculated hashrate is about 10% higher, even on the 6 hours report.
How's that possible?
Btw, I'm dual mining, and It's the same on the second algo.
Isn't it weird?
Jump to: