im playing with overclocking my block erupters and it seems that cgminer is holding back the overclock.
the faster the BE is pushed the more cgminer seems to be holding it back from the speed it should be.
is there some sort of timing option that can be adjusted to help with the extra speed of the BE?
from what I have read the older client used to have some options but its not in the newer clients. any idea's?
PS this is only an issue for overclocked units, my normal ones are fine.
edit.
seems the "--Icarus-timing short" is possibly what I want.
im testing on a windows machine atm. how would I add this in minepeon?
I guess theres a file to edit.
... also I've just added to cgminer master git the code for a TODO I wrote long ago in the Icarus driver ...
It allows you to set a limit to
--icarus-timing short (or
long)
Basically the idea is that if your computer affects the timing due to CPU/Task Scheduling/Swapping/... an optional specified limit wont allow the read_time to go beyond the limit
What it really means is that even if the MH/s is showing wrong due to a bad timing calculation, it will still abort the work at 'limit' and thus will be mining at maximum performance if limit is set appropriately (WU: will show that over a few days)
Historically I have almost always used
--icarus-timing shortNow it will be
--icarus-timing short=100could you explain how to use the times displayed when running short or long to set a custom time?
or am I better off with short as I have multiple hash rates?
my fastest (16Mhz) does this - AMU0 Re-estimate: Hs=2.231016e-09 W=1.409179e-03 read_time=9433ms fullnonce=9.584s
middle (13.5) - AMU3 Re-estimate: Hs=2.646133e-09 W=-5.618202e-04 read_time=11214ms fullnonce=11.364s
slowest (stock) - AMU1 Re-estimate: Hs=2.975410e-09 W=2.931451e-04 read_time=12629ms fullnonce=12.780s