Eligius -vs- Slush -- Hash Rate Differences?

[drewster]

Hello everyone,

I've got a leftover 10.7 GH/s Block Erupter blade I've been testing.  I ran it for a week or so on Slush and now it's been 4 days or so on Eligius.

The blade itself keeps reporting in the 10700 to 10900 MH/s range, but I noticed that Eligius is consistently (so far anyway) reporting lower hash rates.  For example, I also have two junky old GPU miners (12 MH and 80 MH) also pointing to Eligius, so I should be seeing something like 10700 + 12 + 80 = 10792, or 10.792 GH/s. However, I see 3 hour average at 10.13, and 12 hour average at 10.51.

Thoughts?

Thanks!

[1715184634]

1715184634

[1715184634]

1715184634

[1715184634]

1715184634

[1715184634]

1715184634

[1715184634]

1715184634

[DrG]

The pools have no idea with what you're using to hash.  All they see is submitted shares and they calc your rate based on submitted shares.  You can theoretically mine for 5 min and not submit a single share - during those 5 min the pools has to guess your hash rate is 0.

If the 24 hour average is lower that what your machine says you're losing to disconnects, latency issues causing stales, or just dumb luck of not finding shares despite having the power.

Variance of 5% is normal, so those puny miners won't do anything to the stats really.  Anything more should be investigated.

[drewster]

The pools have no idea with what you're using to hash.  All they see is submitted shares and they calc your rate based on submitted shares.  You can theoretically mine for 5 min and not submit a single share - during those 5 min the pools has to guess your hash rate is 0.

If the 24 hour average is lower that what your machine says you're losing to disconnects, latency issues causing stales, or just dumb luck of not finding shares despite having the power.

Variance of 5% is normal, so those puny miners won't do anything to the stats really.  Anything more should be investigated.

Yep obviously I realize that 10-11 GH is nothing. I have other higher end miner also, but have only (so far) seen this discrepancy with the BE Blade, which is why I was curious if there was any sort of "known issue".

Thanks