Optimize your GPU. Find the value the easy way.

NVIDIA GPU's of the 4xx, 5xx, 6xx series normally run better when more than one instance runs / device.
But this is difficult to do manually.

This tool does this automatically and you get a result within 15 minutes.

http://www.efmer.eu/forum_tt/index.php?topic=974.0

Warning, this tool is tested on a limited number of machines. (V 1.0)

It uses the Lunatics optimized exe as a reference.
But you can drop in any version you like as long as you update the config.xml file.


My results:

GTX 295: 260 sec / device = 130 sec / board
GTX 480: 98 sec / device = 98 sec / board
GTX 590: 104 sec / device = 52 sec / board

Interesting to see what a 690 does.
____________
TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

EVGA GTX 560:
Running one at a time the GPU load was in the low 60s, two at a time was low 90s, three at a time was high 90s. Four at a time was low 50s with screen lag. Is this normal (the low 51-54 GPU%)? I ended up cancelling the four at a time test because it was still running after 35 minutes.

Nice little app! Automatic test's result was: count 0.5 fastest.

GTX 690, Devices 2, Count 0.50

Hi Fred,

Cool tool :) can you make it cope with either command line parameters for the exe, or not die if a mbcuda.cfg (x41z) configuration file is present ? (it dies when trying to copy into the slot for some reason, but it does put the file there). It would be handy for finding good settings, for which x41z has a few that the best setting could depend on the count.

Jason
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin

Results with gtx670, driver 304.79, XP 32 bit:

Device: 0, device count: 1, average time / count: 139, average time on device: 139 Seconds (2 Minutes, 19 Seconds)

Device: 0, device count: 2, average time / count: 261, average time on device: 130 Seconds (2 Minutes, 10 Seconds)

Device: 0, device count: 3, average time / count: 389, average time on device: 129 Seconds (2 Minutes, 9 Seconds)

The best average time found: 130 Seconds (2 Minutes, 10 Seconds), with count: 0.50 (2)

1) Why is 130 seconds better than 129? :=)

2) Using the automatic option and a count of .25, it did not test for 4 at a time. I ran that test separately and got:

Device: 0, device count: 4, average time / count: 485, average time on device: 121 Seconds (2 Minutes, 1 Seconds)

So I guess I'll stay with 4 at a time.
____________
Another Fred
Support SETI@home when you search the Web or shop online with GoodSearch and GoodShop

GTX 680, win7x64sp1, driver 304.79, lunatics_x41z_win32_cuda50preview.exe,
at default settings (no mbcuda.cfg or command line switches) :


Device: 0, device count: 1, average time / count: 88, average time on device: 88 Seconds (1 Minutes, 28 Seconds)

Device: 0, device count: 2, average time / count: 155, average time on device: 77 Seconds (1 Minutes, 17 Seconds)

Device: 0, device count: 3, average time / count: 229, average time on device: 76 Seconds (1 Minutes, 16 Seconds)

Device: 0, device count: 4, average time / count: 302, average time on device: 75 Seconds (1 Minutes, 15 Seconds)


Any chance of adding 5 & 6 ?
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin

Hi Fred,

Cool tool :) can you make it cope with either command line parameters for the exe, or not die if a mbcuda.cfg (x41z) configuration file is present ? (it dies when trying to copy into the slot for some reason, but it does put the file there). It would be handy for finding good settings, for which x41z has a few that the best setting could depend on the count.

Jason

Hi Fred,

Cool tool :) can you make it cope with either command line parameters for the exe, or not die if a mbcuda.cfg (x41z) configuration file is present ? (it dies when trying to copy into the slot for some reason, but it does put the file there). It would be handy for finding good settings, for which x41z has a few that the best setting could depend on the count.

Jason

Any chance of adding 5 & 6 ?

1) Why is 130 seconds better than 129? :=)

2) Using the automatic option and a count of .25, it did not test for 4 at a time. I ran that test separately and got:

Device: 0, device count: 4, average time / count: 485, average time on device: 121 Seconds (2 Minutes, 1 Seconds)

So I guess I'll stay with 4 at a time.

Hi Fred,

Cool tool :) can you make it cope with either command line parameters for the exe, or not die if a mbcuda.cfg (x41z) configuration file is present ? (it dies when trying to copy into the slot for some reason, but it does put the file there). It would be handy for finding good settings, for which x41z has a few that the best setting could depend on the count.

Jason

Easy, the parameter is now --device x to set the right device.
I can make a field where you can put additional.

Like -- devices x additional

PS can you give me the x41z for testing?

Or more than 1 app or multiple versions of the dll files.

So I'm going to try 4 wu's each on my GPU's (no HT, 2 core's)

So I'm going to try 4 wu's each on my GPU's (no HT, 2 core's)

0.5 should be the best.

Well, I can't get it to work. I have one NVIDIA GT 520 installed. When I run the program with the default "Devices 1", "Count 0.50", I get this:

Starting test: (lunatics_x41g_win32_cuda32_perf.exe)
25 August 2012 - 20:56:50 Start, devices: 1, device count: 2
25 August 2012 - 20:57:07 Program failed to start on slot: 0
25 August 2012 - 20:57:07 Program failed to start on slot: 0
25 August 2012 - 20:57:08 Program failed to start on slot: 0
25 August 2012 - 20:57:08 Program failed to start on slot: 0

So ... what am I not doing correctly? (Yes, I stopped BOINC Manager before executing the performance utility).

____________