Few questions about NH Vs Zpool:
Are you mining the same algos in both pools ? If not what algos are you mining in both ?
Are you using the same miners and settings ?
Are you using Nemos w/nicehash pool ?
Does you estimated 11% difference accounts for Nicehash fees to pay external wallets, as this would be the most similar of using zpool ?
Looking forward to your response, thanks for sharing your findings.
Most of your questions are answered in this post:
https://bitcointalksearch.org/topic/m.30205761. The comparisons I am doing are rather informal and should be treated as such. Any difference of 5% or less should be considered a tie on account of the rather low hashrate of a single GTX 1080 and I tend to runs these tests for 24, 48 or 72 hours when 7 days or more would likely be necessary. But since you all aren't paying me to do these tests I get to pick the contestants, run time etc...
I am not using NemosMiner with NiceHash's pool - that doesn't make a lot of sense to me, frankly; miner scripts like NemosMiner along with algo-switching pools like Zpool, MiningPoolHub, HashRefinery, etc., are /alternatives/ to NiceHash, after all.
The running total of BTC does not take into consideration the 2% fee that NH charges to move "theoretical BTC" from your local miner to their wallet (no BTC is actually transferred, hence "theoretical"). I have a Coinbase account so I can transfer from the NH wallet to there for free.
I have no good explanation for why Zpool/NemosMiner are so far behind NH, but prior to this comparison I tried out Zpool in "single algo, convert to a coin besides BTC" with two different coins (same algo - Lyra2v2) and got excellent results. I therefore feel like the pool is trustworthy - it's not intentionally shortchanging me, in other words - so the difference in earnings may very well point to a flaw in the algo-switching.
For example, it takes vertminer - a specialized fork of ccminer strictly for lyra2v2 - a good 20 minutes before it gets fully up to speed on my 6x GTX 1060 rig: it starts out at around 120 MH/s and climbs to 133 MH/s - that right there is 11%.
I've noticed something similar with Neoscrypt, both with HSRminer and ccminer KlausT.
But as for why this is occurring, I have no clue.