Cheers
I did. Accourding to my testing 3.2 clocked at 300 is making about 68000 compared to 3.1 70500. 24 hours run. I downgraded to cgminer 3.1. I do not know what is the reason, but there is performance decrease.
Will Anyone else to share the cgminer 3.2 results?
Hi,
I noticed that too and asked CKolivas. He replied:
The old avalon code lied about the hashrate and lied about the hardware errors. It counted hardware errors as hashrate (and since it's a hardware error it can't be valid hashes that it's doing) and didn't count "no matching work" scenarios as hardware errors. So the new code will appear to have a lower hashrate and a higher hw error count, but in fact it's doing more useful work and just not lying about the rates (along with all the other benefits in the new code).
https://bitcointalksearch.org/topic/m.2406402