tested, and i see a good hashrate on the miner side, but seems to be only 150H/s on pools side (both suprnova and blockquary)
Yes that is a problem. I don't understand, the hashrate calculation is very simple and the hashes_done calculation
is all self contained in the algo source file. scanhash_hodl is counting the collisions and the miner thread measures
the time and it's a simple division. I don't see where it could go wrong.
It happens with both AES_NI and NON_AES_NI implementations of hodl. It doesn't
happen with any other algo.
If the hashes_done calculation is wrong then it is in code was copied as-is from the original hodlminer.
If the time is wrong it is in code that is the same for all algos.
The only other thing I can think of is phantom accepts or silent rejects. Either the miner is dsplaying shares that
were never submitted or not reporting shares that were rejected.
It happens with both AES_NI and NON_AES_NI implementations of hodl. It doesn't happen with any other algo.
The pool reported hashrate appears to be inline with both precedessors, although it's hard to be sure with the flunctuations.
I've seen it as high as 400 H/s with both Wolf and opt/wolf on an i7-4790K and i7-6700K repsectively.
I will do some instrumenting to gather data to see if I can figure out what's going on.
FYI, I haven't maintained build.sh, so YMMV