I would like to know the best/fastest settings for my hardware (E7600 & GTX260).

Currently I have the 263.06 (dev-) driver installed (min recommended driver for APv6 OpenCL).
Or I should go with the latest WHQL driver (still with OpenCL BUG, so need to free one CPU-thread?)?

Currently I have set (AMD/ATI recommendation for >12 CUs, GTX260 have 27 CUs):
<cmdline>-unroll 12 -ffa_block 8192 -ffa_block_fetch 4096 -hp -instances_per_device 1</cmdline>

(-instances_per_device just for <stderr_txt> ;-)


I should set and test:

-unroll 12 -ffa_block 7168 -ffa_block_fetch 3584
-unroll 12 -ffa_block 6144 -ffa_block_fetch 3072
-unroll 12 -ffa_block 5120 -ffa_block_fetch 2560
...

-unroll 12 -ffa_block 9216 -ffa_block_fetch 4608
-unroll 12 -ffa_block 10240 -ffa_block_fetch 5120
-unroll 12 -ffa_block 11264 -ffa_block_fetch 5632
...

-ffa_block: +/- 1024, -ffa_block_fetch: 1/2 of -ffa_block ?

If I found the fastest settings, I should test +/- 1 -unroll, for to find again the fastest settings?

The best would be to compare 0 % blanked WUs?

Thanks.


* Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---

Dumb question: If you are using an Nvidia card (GTX 260) why are you concerned with stuff for ATI cards? Or did I miss something?

---

postid=1385168 and following.

In the ReadMe_AstroPulse_OpenCL_NV.txt file are only AMD/ATI cards mentioned.

I don't know if the cmdline recommended settings are also for NV cards ..


* Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---

Your NV 260 is a mid range card.

So normal settings would be -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536.
Given the fact pre Fermi`s can only handle one instance you can increase the settings.

Your settings are already improved -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096.

You can use -unroll 12 -ffa_block 12288 -ffa_block_fetch 6144.
Evenso you could try -unroll 14 to 16 but use at your own risk.

Beware if you experience overflow tasks reduce the settings again until you find the sweet spot.

As always your milage might vary.

I will rework the NV readme until the next release.

BTW: You dont need to post in 2 threads.

Mike

---

With each crime and every kindness we birth our future.

I deleted the whole <cmdline> in app_info.xml file.

Made an ap_cmdline.txt file in setiathome.berkeley.edu folder inserted the parameters without <cmdline> & </cmdline>.

The NV OpenCL AP r1843 don't use the parameters.
(Only if I set parameters between <cmdline> & </cmdline> in app_info.xml file.)

What did I wrong?

Thanks.


* Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---

I deleted the whole <cmdline> in app_info.xml file.

Made an ap_cmdline.txt file in setiathome.berkeley.edu folder inserted the parameters without <cmdline> & </cmdline>.

The NV OpenCL AP r1843 don't use the parameters.
(Only if I set parameters between <cmdline> & </cmdline> in app_info.xml file.)

What did I wrong?

I had the same problem, solved it by putting the parameters in the file named

ap_cmdline_win_x86_SSE2_OpenCL_NV.txt

---

Aloha, Uli

I deleted the whole <cmdline> in app_info.xml file.

Made an ap_cmdline.txt file in setiathome.berkeley.edu folder inserted the parameters without <cmdline> & </cmdline>.

The NV OpenCL AP r1843 don't use the parameters.
(Only if I set parameters between <cmdline> & </cmdline> in app_info.xml file.)

What did I wrong?

I had the same problem, solved it by putting the parameters in the file named

ap_cmdline_win_x86_SSE2_OpenCL_NV.txt

Correct.
Its already in your project folder.

---

With each crime and every kindness we birth our future.