Closed hashbullet closed 5 years ago
It appeared again today. 124 failed over 9hrs of mining. Used C3pool this time. (issue was created based on Pascal pool mining).
Failed shares are not like rejected shares. Failed shares are locally duplicates. Meaning, you have many cores and 2 of them found a valid nonce within the same work package. RHhminer wont submit the duplicates because then the pool will reject them for their are duplicates ! This is inherent to the nature of RandomHash cuz and there is no real way to make this number go lower. In V1.4, I managed to reduce this from 1.2% to 0.7% on average, but that is it.
Ok. in that case I will live with this.. as I indicated before, I was never experienced a failed share in v1.3. so was not sure whether it is a bug or random.!
Started using rhminer v1.4 and found a lot of failed hashes due to duplicate. The amount of failed hash is related to the mining speed (resources). Currently a cpu only mining (i5 8400 - 6 cputhreads) reported 13 failed in ~30mins. a CPU + GPU mining reported more failed hashes. The duplicate submission typically happen 2-3 submission after the actual (first accepted) submission. where as in rhminer v1.3 din't report a single failed hash over multiple weeks on the same hardware.
the same behavior noticed both in CPU only and Volta versions (the only two I tried).