[QUOTE=flashjh;294446]
[/CODE]2.00 is very fast, even with -t. I'm getting just over 15 hours per DC. Too bad my new GTX680 is not worth opening up... any gamer out there want to trade an unopened 680 for a 580+some cash :smile:[/QUOTE]

Good luck with that. I expect someone will want it.

[url]http://mersenne.org/report_exponent/?exp_lo=26232301[/url]

...How did you get the good result before the bad one? :huh:

[QUOTE=flashjh;294446]I've had 4 2.00 sucesses and 1 mismatch. I don't know for sure what caused the mismatch, but I had a driver failure that Win7 recovered from, so that's probably it (I caused it by closing CuLu too soon after starting)[CODE]
M( 26232301 )C, 0x[COLOR=red]251f67a97a93197a[/COLOR], n = 1474560, CUDALucas v2.00
M( 26232803 )C, 0xd00b85dcfaee04b3, n = 1474560, CUDALucas v2.00
M( 26232301 )C, 0x[COLOR=lime]040e8dd990e95b17[/COLOR], n = 1474560, CUDALucas v2.00
M( 26240933 )C, 0x68d29225ff867aa5, n = 1474560, CUDALucas v2.00
M( 26296561 )C, 0x60db292b00734623, n = 1474560, CUDALucas v2.00
[/CODE]

2.00 is very fast, even with -t. I'm getting just over 15 hours per DC. Too bad my new GTX680 is not worth opening up... any gamer out there want to trade an unopened 680 for a 580+some cash :smile:[/QUOTE]

could try ebay, $600+ is the current selling price.

[QUOTE=Dubslow;294456][URL]http://mersenne.org/report_exponent/?exp_lo=26232301[/URL]

...How did you get the good result before the bad one? :huh:[/QUOTE]
In my file it was bad then good, PrimeNet shows it different; I don't know why. Basically I got the Bad DC, so I ran a TC to get the good result.
[QUOTE=kladner;294450]Good luck with that. I expect someone will want it.[/QUOTE]

[QUOTE=bcp19;294459]could try ebay, $600+ is the current selling price.[/QUOTE]

I'm sure it will sell; I can't list it until I get home. Ironically, I haven't even seen it yet and I need to sell it. Here's to hoping nVidia does [I]much[/I] better with GK110.

[QUOTE=bcp19;294321]
Is it possible in future versions to 'clean up' the FFT selection?[/QUOTE]
[code]
CUFFT_Z2Z size= 1081344 time= 17.912073 msec
CUFFT_Z2Z size= 1179648 time= 3.668577 msec
CUFFT_Z2Z size= 1277952 time= 23.579775 msec
CUFFT_Z2Z size= 1376256 time= 4.184882 msec
CUFFT_Z2Z size= 1474560 time= 4.181284 msec
CUFFT_Z2Z size= 1572864 time= 4.305398 msec
CUFFT_Z2Z size= 1671168 time= 29.604942 msec
CUFFT_Z2Z size= 1769472 time= 4.611794 msec
CUFFT_Z2Z size= 1867776 time= 35.498314 msec
CUFFT_Z2Z size= 1966080 time= 5.232563 msec
CUFFT_Z2Z size= 2064384 time= 6.078244 msec
CUFFT_Z2Z size= 2162688 time= 30.571829 msec
CUFFT_Z2Z size= 2260992 time= 45.150196 msec
CUFFT_Z2Z size= 2359296 time= 6.338501 msec
CUFFT_Z2Z size= 2457600 time= 8.342790 msec
CUFFT_Z2Z size= 2555904 time= 37.028366 msec
CUFFT_Z2Z size= 2654208 time= 8.117778 msec
CUFFT_Z2Z size= 2752512 time= 7.537333 msec
CUFFT_Z2Z size= 2850816 time= 63.291031 msec
CUFFT_Z2Z size= 2949120 time= 7.693821 msec
[/code]
Multiples of 98304 is unstable performance.

Another 2 successful DCs, CudaLucas v2.0, -f 1474560, for 26276197 and 26247433.

I just completed my first full run on CuLu (2.0) of a DC. Residue matched the original LL and Jerry's good DC. This gives me confidence to try some "real work" now.

[CODE]M( 26229943 )C, 0x769161872540121c, n = 1572864, CUDALucas v2.00[/CODE]

[QUOTE=kladner;294514]I just completed my first full run on CuLu (2.0) of a DC. Residue matched the original LL and Jerry's good DC. This gives me confidence to try some "real work" now.

[CODE]M( 26229943 )C, 0x769161872540121c, n = 1572864, CUDALucas v2.00[/CODE][/QUOTE]

Did you try -f 1474560. It will increase your throughput, just use -t and watch your error.

[QUOTE=flashjh;294517]Did you try -f 1474560. It will increase your throughput, just use -t and watch your error.[/QUOTE]

No, I didn't. I'm still baffled by selecting FFT sizes. I messed around a little, but only succeeded in terminating the program.

I've started another 26M DC. The automatic system set 1572864. I will try it with 1474560. Thanks for the suggestion!

EDIT: This is weird. I have this command line: [CODE]start CUDALucas2.00.cuda3.2.sm_13.x64 -c 10000 -f 1474560 -t -s check -polite 1 -k worktodo.txt[/CODE]

But CuLu continues to start with 1572864.

[QUOTE=kladner;294524]No, I didn't. I'm still baffled by selecting FFT sizes. I messed around a little, but only succeeded in terminating the program.

I've started another 26M DC. The automatic system set 1572864. I will try it with 1474560. Thanks for the suggestion![/QUOTE]

It will terminate with a FFT that causes too high of an error. If you read back through the thread you can see some examples. CuLu also includes a FFT test:

cudalucas.exe -cufftbench [I]start stop distance[/I]

start: beginning exponent
end: stop exponent
distance: size between FFTs (32768 is normal)

Once you run that, you can use the fastest FFTs and run each one until you get it stable. For me, all the FFTs that were faster than 1572864 caused errors except 1474560. So far with -f 1474560 -t -polite 0 I have had very good runs excpet one (which was my fault), but the TrippleCheck was good.

Jerry

Thanks Jerry, for the explanation. I'll go back and run -cufftbench and try to get a handle on things. But at the moment, it ignores -f for some reason. I'll get back to it in a bit.