Quote from: edonkey on May 09, 2014, 01:51:05 PM

Quote from: dloganbill on May 09, 2014, 11:56:49 AM

Quote from: walther1337 on May 09, 2014, 10:39:03 AM

Is 24 hours really enough for auto-tune to do its work? I thought it could take a while to figure out the optimal clocks.

If it takes over 24 hours to achieve best results, I'm not interested. That would mean every pool change, software update, reboot, power blip, etc would require it to start from scratch. That doesn't work for me.

My understanding is that the auto tune feature maximizes the frequency for the hardware, and that that is unrelated to pool changes.

You can use the API to obtain the frequency values after auto-tune is done and use those to create the command line for any subsequent runs. In fact, this person coded a PHP script to do that:

https://bitcointalk.org/index.php?topic=482352.msg6603449#msg6603449

Note that in order to tell when auto-tune is done, you should use the --debug option.

API now has autotune status for each chip.
0 = autotune off
1 = autotune running
-1 = autotune stopped
So it will be easy to save the resulting frequencies when autotune finished.