I found a MAX pool that does not properly weight the share difficulties and basically only counts total submitted shares, they use vardiff that starts fresh with each connection and re-calcs after 60 seconds, but during that first run I can get 200-400 shares submitted and make 5-7% of the mined block...
The --time-limit command takes a REALLY long time to close out, anywhere between 5-30 seconds, normally this won't be much total down time if you are doing a 30 minute cycle but it can be a very large chunk of time if you are doing a 60-80 seconds restart time...
I've written a batch script to kill and restart CUDAMiner every 60 seconds, this ends the process and restarts very quickly with very little perceivable downtime. For thos that are interested...
Win Vista and higher only due to use of TIMEOUT command.
@echo off
set app="cudaminer.exe"
set limit=60
:start
start "" /min %app% -i 0 --algo=keccak -R 2 -L 256 -l K1022x32 -q -C 2 -o stratum+pooladdress -O workername:password
timeout %limit%
taskkill /im %app% /f
goto start
Much faster turnaround in Windows.
@Christian - Not sure why it takes so long for the --time-limit command to shut down CUDAMiner, might be worth looking into.