I've got quite a circus going on right now, actually, with 4 separate rigs doing different things at the same time. The relevant comparison here is between Nemosminer on MiningPoolHub vs. NiceHash Miner straight out of the box, so to speak. Both Nemosminer/MiningPoolHub and NiceHash are auto-switching between algorithms - and not always choosing the same one, I might add - and each get their own GTX 1080 to use (running on separate computers).
I also have a 3rd rig running a Neoscrypt miner (Gateless Gate - AMD only) on Zergpool which auto-switches between multiple coins of the same algorithm and converts all proceeds to BTC, just like Nemosminer and NiceHash. I am mainly testing Zergpool out of curiosity, but am prepared to be surprised should it show up the multi-algo auto-switching miners.
Yeah that's quite the circus alright. From what I've observed, NH is very prone to price manipulation for a number of algos. Due to this, I've decided to just limit algos for both AHP and NH, in hopes of finding a combination that isn't going to result in a lot of downtime (neoscrypt for example takes quite a while to "warm up").
Thoughts on hsrminer's (and therefore, Nemo's) numbers for neoscrypt? Some people are saying it's pumped up, but I'm not mining neo on AHP, and NH doesn't have precise hash numbers outside of benchmarking. Actually, as I write this, I'm wondering if benchmarking on NH is client or server-side. With people saying hsrminer falls off severely in hash after 15-60mins, I'm wondering if that was to pump up benchmark numbers before actually mining.
Yeah, NH can bring such a huge amount of hashpower to bear on any algo, so if the coin that is the "flavor of the minute" has a tiny float (er, circulating supply) then difficulty skyrockets, locking out the small miners while NH simultaneously shoots itself in the foot and vacuums all the coins. Their business model is kind of nutty, actually.
As for hsrminer, almost every time I've run it - note that "almost" - it starts off roaring then mysteriously drops by a certain percentage after awhile. Usually the hashrate drops after 1-3 hours, but there have been times where the hashrate was stable for more than 6 hours, so I'm not sure what to think about that.
However, in every single case so far the actual earnings have been substantially lower than the hashrate would otherwise have me believe; in my latest test I earned 76% of the coins that hsrminer said I would after 8 hours of run time on a pool that finds a block every 4 minutes (so a short run time is less likely to skew the earnings). That would make hsrminer slower than its closest competitor, ccminer-klaust 8.19, but I will need to run the latter on the same pool for the same length of time to confirm that.
As for NH's benchmarking, I can't say for sure whether it is based on client-side reported hashrate, or server-side reported shares... The latter would be more accurate but people might complain about getting shortchanged enough to make NH not use it.