![]() |
|
|
#12 |
|
Apr 2012
Berlin Germany
3·17 Posts |
Tried to find the max FFT length with my GTX 680 4GB
the cufftbench crashes near 30M is this just normal? |
|
|
|
|
|
#13 |
|
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 -89<O<-88
3×29×83 Posts |
I've seen it crash before, but I don't know enough about how it works to try and fix it. There are no known reports of actual LL tests crashing, so I haven't really put any thought into it.
|
|
|
|
|
|
#14 |
|
"Kieren"
Jul 2011
In My Own Galaxy!
2×3×1,693 Posts |
CUDALucas has shown itself to be sensitive to memory errors if the memory clock is too high. This is known to happen on some GTX 570's even when they are running at nVidia's specified memclock. Get MSI Afterburner and try cutting the memory speed by 100 or 200 MHz and run the test again.
I could not complete the CuLu self-test until I slowed my 570's memory from 1900 to 1800 MHz. |
|
|
|
|
|
#15 | |
|
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 -89<O<-88
3·29·83 Posts |
Quote:
|
|
|
|
|
|
|
#16 | ||
|
"Bill Staffen"
Jan 2013
Pittsburgh, PA, USA
23×53 Posts |
Quote:
Quote:
|
||
|
|
|
|
|
#17 | ||
|
"Bill Staffen"
Jan 2013
Pittsburgh, PA, USA
23×53 Posts |
In this run I did 32k increments from 17M to 22M+1. No real surprises here: the M markes are all the lowest numbers. I deleted numbers from the list below that had better numbers further on, but after 18M (11 seconds) I just put down all times < 16 seconds for reference. The full log is attached. After that I ran it till it crashed at 1M increments.
Quote:
Quote:
|
||
|
|
|
|
|
#18 | |
|
"Bill Staffen"
Jan 2013
Pittsburgh, PA, USA
23×53 Posts |
I'll edit this again in a bit, I was trying some math, but I got the inverse of what I wanted. Whoops!
EDIT: I give up, I don't know where the tradeoff is between bigger numbers and lower speed. EDIT2: Ok, one more try at my crazy efficiency crud. Quote:
Last fiddled with by Aramis Wyler on 2013-02-08 at 23:47 Reason: bad math! |
|
|
|
|