Forum > GPU crunching
GTX 460 superclocked
Ghost0210:
just going through the tasks I hadn't reported, hoping to get definitive times from my testing with mulitple tasks running
Ok, after running through the tasks I haven't yet report and the online testing I done with whichever random VHAR tasks Boinc decided to throw at me next (I'll have to set up some real test conditions when I get the time)
So, first of all I need to slap myself for not doing this before I first posted and my apologies Frizz23 ::)
Revised and accurate average times:
Like I said, all VHAR and all different tasks:
1 task at a time::each task took ~ 200 seconds to complete
2 tasks at a time::each task took ~330 seconds to complete[revised time]
3 tasks at a time::each task took ~520 seconds to complete[revised time]
So tasks completed in an hour using the above times:
1 task at a time:: 3600 / 200 = 18 tasks an hour
2 task at a time:: 3600 / 330 * 2 = 21.8 tasks an hour
3 tasks at a time:: 3600 / 520 * 3 = 20.7 tasks an hour
So the best throughput (highest number of tasks per hour) on my 465 works out to 2 at a time, could well be different on your 460 if you decide on one, but I agree with Jason, its a good card and as nVidia release more documentation on it, it will only get better
sunu:
You guys that run 2 or 3 tasks at a time in your fermi cards, what RAC does that give to your cards?
As for the question about the 768MB card I would advise against that. 768MB memory seem quite small nowadays. Maybe 2-3 years ago yes, but not now. Get the higher memory model.
Frizz:
How can I see in the WU XML file whether or not a WU is a VHAR?
Shorties (are they always VHARs?) usually run in 5:50 on my GT 240. So it's about 10 per hour.
Somehow I can't believe the 465 is only 2x my cheapish GT 240 ...!?
Jason G:
--- Quote from: sunu on 10 Aug 2010, 05:22:46 pm ---You guys that run 2 or 3 tasks at a time in your fermi cards, what RAC does that give to your cards?
--- End quote ---
On the 480, with x32f 3.1, running on a E8400 Oc'd to 3.6GHz, I just passed 21000 today. The CPU is running AKv8b with occasional AstroPulse... I think it should start to level off soon, but don't know for sure. I'm finishing two midrange tasks on the 480 in about 9-12mins, or two shorties in ~3 mins. single task times were ~7-8 mins & ~2mins for Mid AR & shorty respectively.
--- Quote ---As for the question about the 768MB card I would advise against that. 768MB memory seem quite small nowadays. Maybe 2-3 years ago yes, but not now. Get the higher memory model.
--- End quote ---
I agree. For me it's the memory bus width though. With this much processing power at hand memory bandwidth will nearly always be the primary concern, and nVidia wisely have included some special cache control mechaisms in the driver API ( which we can't switch to yet, until I have the complete set of freaky powerspectrums, still on track for christmas 2010 ;), later to be replaced with a freaky powerspectrum cascade kernel to maximise cache benefits)
Jason G:
--- Quote from: Frizz23 on 10 Aug 2010, 05:34:33 pm ---How can I see in the WU XML file whether or not a WU is a VHAR?
Shorties (are they always VHARs?) usually run in 5:50 on my GT 240. So it's about 10 per hour.
Somehow I can't believe the 465 is only 2x my cheapish GT 240 ...!?
--- End quote ---
As you get faster on GPU, a larger proportion of shorty run time is CPU time ;) That's a fairly fixed overhead between tasks & largely machine dependant.
You can search for the word angle in the task file using a text editor. The true angle range of the task is there. It's easier just to look at the stderr task output after the task reports (and the servers are up) though. There is an exact threshold above which is considered VHAR, and that makes shorties. I forget exactly what that threshold is, around 1.1 I think. Joe keeps that kind of information around here :D. Above that, whatever it is, they all tend to take pretty much the same short time to process.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version