Optimize your GPU. Find the value the easy way.

Here are my tests running on a 570 with different CUDA apps.

For some reason running 4 tasks didn't complete on either the 41z cuda 3.2 or 41z cuda 4.2.

Starting automatic test: (x41x_winx64_cuda41)
Device: 0, device count: 1, average time / count: 127, average time on device: 127 Seconds (2 Minutes, 7 Seconds)
Device: 0, device count: 2, average time / count: 203, average time on device: 101 Seconds (1 Minutes, 41 Seconds)
Device: 0, device count: 3, average time / count: 290, average time on device: 96 Seconds (1 Minutes, 36 Seconds)

Starting automatic test: (x41x_winx64_cuda42)
Device: 0, device count: 1, average time / count: 124, average time on device: 124 Seconds (2 Minutes, 4 Seconds)
Device: 0, device count: 2, average time / count: 198, average time on device: 99 Seconds (1 Minutes, 39 Seconds)
Device: 0, device count: 3, average time / count: 285, average time on device: 95 Seconds (1 Minutes, 35 Seconds)
Device: 0, device count: 4, average time / count: 469, average time on device: 117 Seconds (1 Minutes, 57 Seconds)

Starting automatic test: (x41z_winx64_cuda42)
Device: 0, device count: 1, average time / count: 128, average time on device: 128 Seconds (2 Minutes, 8 Seconds)
Device: 0, device count: 2, average time / count: 198, average time on device: 99 Seconds (1 Minutes, 39 Seconds)
Device: 0, device count: 3, average time / count: 284, average time on device: 94 Seconds (1 Minutes, 34 Seconds)

Arvid
____________
Arvid Almstrom

Tool version 1.2

Card: GTX 460


Results:
Starting automatic test: (x41g)
04 September 2012 - 21:42:57 Start, devices: 1, device count: 1 (1.00)
04 September 2012 - 21:47:27 Runtime: Device: 0, count: 0, 265 seconds
04 September 2012 - 21:47:27 Device: 0, Count: 0, finished.
Ready ---------------------------------------------------------------------
Results:
Device: 0, device count: 1, average time / count: 265, average time on device: 265 Seconds (4 Minutes, 25 Seconds)
Next ---------------------------------------------------------------------
04 September 2012 - 21:47:29 Start, devices: 1, device count: 2 (0.50)
04 September 2012 - 21:56:02 Runtime: Device: 0, count: 0, 510 seconds
04 September 2012 - 21:56:02 Device: 0, Count: 0, finished.
04 September 2012 - 21:56:12 Runtime: Device: 0, count: 1, 520 seconds
04 September 2012 - 21:56:12 Device: 0, Count: 1, finished.
Ready ---------------------------------------------------------------------
Results:
Device: 0, device count: 2, average time / count: 515, average time on device: 257 Seconds (4 Minutes, 17 Seconds)
Next ---------------------------------------------------------------------
04 September 2012 - 21:56:13 Start, devices: 1, device count: 3 (0.33)
04 September 2012 - 22:08:10 Runtime: Device: 0, count: 0, 711 seconds
04 September 2012 - 22:08:10 Device: 0, Count: 0, finished.
04 September 2012 - 22:08:14 Runtime: Device: 0, count: 2, 715 seconds
04 September 2012 - 22:08:14 Device: 0, Count: 2, finished.
04 September 2012 - 22:08:17 Runtime: Device: 0, count: 1, 718 seconds
04 September 2012 - 22:08:17 Device: 0, Count: 1, finished.
Ready ---------------------------------------------------------------------
Results:
Device: 0, device count: 3, average time / count: 714, average time on device: 238 Seconds (3 Minutes, 58 Seconds)
Next ---------------------------------------------------------------------
04 September 2012 - 22:08:19 Start, devices: 1, device count: 4 (0.25)
04 September 2012 - 22:24:12 Runtime: Device: 0, count: 0, 945 seconds
04 September 2012 - 22:24:12 Device: 0, Count: 0, finished.
04 September 2012 - 22:24:20 Runtime: Device: 0, count: 1, 953 seconds
04 September 2012 - 22:24:20 Device: 0, Count: 1, finished.
04 September 2012 - 22:24:22 Runtime: Device: 0, count: 2, 955 seconds
04 September 2012 - 22:24:22 Device: 0, Count: 2, finished.
04 September 2012 - 22:24:22 Runtime: Device: 0, count: 3, 955 seconds
04 September 2012 - 22:24:22 Device: 0, Count: 3, finished.
Ready ---------------------------------------------------------------------
Results:
Device: 0, device count: 4, average time / count: 952, average time on device: 238 Seconds (3 Minutes, 58 Seconds)
The best average time found: 238 Seconds (3 Minutes, 58 Seconds), with count: 0.33 (3)
____________

Tool version 1.2

I was called that once in high school.

thanks for the info.

Full day of running about 600 or more completed and only those 2 errors so far.
rac over 4000
CPU has started crunching late last night.
so far so good at 3 wu each
Gtx 670 gtx 470 ( win 7 64 bit) Nvidia 306.02
____________

made it thur a day of server down 270 + tasks reported when server came up.
with plenty in cache. First time ever. I also go a few astopusle wu ( 155 min runtimes once cpu freed up) Let the good times roll.


____________

@Snowmain

that is a very interesting list ;) thanx

in the next some weeks my Nvidia-GT630 get a new friend that is not in the list.
im courious about the WU's/$ :D

greetings
ralf
____________
Boinc runs here on:
Intel i7-3770K (Limited to 6 Cores)
Nvidia GT-630 (Fermi)

@ The Chosen.....and everybody else.


For my 2 cents the 229$ on the gtx 570 is the price performance Delta.
My hope is that Sept 16th when the newest GTX 650 and 660 come out it will push down the price of gtx 570. Here's hoping.

Finding power consumption #'s on the mobile processors was very difficult. Since the likelyhood of them being used is so low when I foujnd a number I didn't look any further...so they very well could be wrong( as any of these numbers could be wrong).
____________

This brings up another question: Since there is no Lunatics NVIDIA GPU app for Astropulse (as of yet...), will my machine run GPU Astropulse WU's using the standard SETI app, or do I need to add something the the app_info file? And if so, what? The answer may be out there somewhere, but a search here and on the Lunatics site hasn't turned it up...

yes, once you enable AP tasks via your web preferences, your host should eventually download the stock nVidia OpenCL Astropulse binaries, and tasks will of course follow when they become available.

Thanks for the reply. The stock binaries haven't appeared yet, but maybe I need to de-select AP, update, and then re-select AP.

you really only need an entry for it in the app_info.xml if you want to run multiple tasks in parallel/increase GPU utilization/decrease CPU utilization/mitigate GUI lag/etc.

This brings up another question -- where can I find info on what all can be done via settings in the app_info.xml file??? Can multiple stock AP tasks be executed in the GPU? I didn't think that was possible...