However, 11.2s is calculated based on the Icarus mining at 2.6316ns per hash
(which of course means 5.2632ns per pair of hashes)
Once you have a new correct nanosecond value for your faster bitstream (lets say it was 2.2222ns), you simply start cgminer with the option:
--icarus-timing 2.2222
Ok so doing a temp update to the 200mhz bitstream I recalc'd and get these values :
2.500 10.744
so would I be right to set --icarus-timing 2.5000=10.8
or do i leave the second value at the default and just have the 2.5000 without the =10.8 ?
Preliminary results seem to have bumped the U/rate up from 20-21 to about 21-22, so its the expected 5%
Power consumption seems unchanged.
[update]Setting --icarus-timing 2.5000=10.8 yielded results of about 1200 shares per hour, similar to the default 190mhz bitstream which usually nets about 1260 shares per hour
Setting --icarus-timing 2.5000 is yielding about 1328 shares per hour which is the expected 5% bump going from the 190mhz up to the 200mhz bitstream
kind regards
