Quote from: Doucesti on November 12, 2018, 04:12:33 PM

Quote from: todxx on November 12, 2018, 07:08:26 AM

Can you guys provide a bit more information?
How long did you run the miner?
How many shares were submitted to the pool during your test?
Where any shares rejected? Were there any hw errors?
How does the pool report hashrate? Are you looking at a 24 hour average reported by the pool?
Which of the 3 hashrates printed by the miner are you comparing to the pool hashrate?

Can you post the output of the miner at the end of your test?

I've run the miner for a good 4-5 days on nanopool, each time I checked, saw the average xmr mined approx. 7% lower then whattomine and cryptocompare resulted (with deducing pool and dev fee) and hashrate 6% lower.
I've run on supportxmr for 24hours, still 6% lower. But now It seems more reasonable after 48 hours... will update!

I don't know about shares, supportxmr adds all my other miners.
No share rejected, no hw errors.
I am comparing the last hashrate of the miner, (pool)

Maybe nanopool was the problem, maybe because I have other, less powerfull miners on it?

You know, this is a little interesting. Nanopool has a broken rpc implementation which causes issues when e.g. submitting two or more shares in quick succession. Now, we assumed that we'd still get replies for all submitted shares, but there could cases where they actually drop rpc requests. I didn't do the fix though, need to check with todxx.

Comparing pool payouts is a different thing though. Unless you're sure the pools hit exactly 100% avg luck over the same period, it doesn't say much. The poolside hashrate displayed in the miner should match your miner hashrate minus dev fee and any rejected shares. If that looks good, we can't really do much more from a miner dev perspective. If that number is ok, but the pool reports a different hashrate, something is fishy.