... the actual rate is the 8.22MH/s, but it just reports the 528kH/s (well, in this case since there are two pools operating, it'd be like 7mh/s on pool 1 and 1.2mh/s on pool 2... but the local rates still don't add up to the pool rate). i installed the
https://github.com/Neisklar/quarkcoin-hash-python but that only fixes my own miner, not what the pool reports? re: if I start mining with one of my servers, the local rate goes up a ton
That python module is only for calculating the blockhash using the quark algorithm for p2pool and the blockexplorer, it's not for a miner.
There are minerd version out there which have a small bug, that they only report 0.0039 Diff or higher shares.
It's fixed (and i'm sorry for that i accidentially hide it somewhat in the commit messages) in the quarkcoin cpu miner repo
https://github.com/Neisklar/quarkcoin-cpuminer/commit/b1af442712ee82fe9764df3812d134a99e11e3f2.
That can be the cause of wrong reported values.
I think i did not update the binaries i released, since at that point, i though that such a low diff would never be happen again and did not though about the p2pool and the pseudo shares. (You could workaound in the p2pool by raising the lowest pseudoshare target)
ah, yeah, that makes sense, not sure why i didn't think of it. can just see it from my own graphs, from when hashrate dropped
i probably will change it later, was thinking about making time between shares 30s as well (up from the 20s i have it set to atm) (ed: there's also quite a few new commits to p2pool i want to put in as well)