AutoTune - Thirtybird/YACMiner GitHub Wiki
"auto-tune" the raw intensity/lookup gap
-
should worksize be tweaked by this? (thoughts are no, and just suggest everyone use worksize of 32)
-
-
can worksize be adjusted on-the-fly?
-
-
if a HW error occurs, drop the R by worksize
-
how to determine if R should be increased?
-
-
after x number of seconds/minutes without a HW error
-
-
-
need to keep track of the lowest R for a given N that gives HW errors so it isn't auto-bouncing up and down
-
-
different types of cards will accept different divisors of nFactor
-
-
with a worksize of 32, 5XXX cards just need to be a multiple of 32
-
-
-
7XXX cards may be the same way
-
-
-
GCN cards can tweak in increments of 8
-
-
can determinations of baseline R factor be made based on N factor, buffer-size and number of shaders CU's? (look to xI code to determine count)
-
-
3/18/2014 - absolutely can. Now have formula to determine max -R for a given N, BS and LG
-
-
-
high shaders & low memory = higher LG
-
-
is there a way to determine if memory for the threads is in dedicated memory or being swapped out to dynamic memory?
-
(likely)should this setting play with lookup-gap at all?
-
(likely)should this setting play with worksize at all?
-
reset the HW counter for a GPU if the R has been changed
-
auto-tune process may need to involve CPU checking of hashes for a period of time even if they do not meet the minimum difficulty to know if it's generating HW errors
-
-
or check any hash of difficulty 1
-