Yeah, at a certain point you get diminishing returns for fine-tuning parameters. I didn't bother pushing unroll too hard, I only used 11 because the HD 6950 has 22 compute units.

For the ffa parameters, 16384/8192 crashes (presumably too much memory required or whatever), and didn't bother trying to push further than 8192/4096.

For the record, the HD 6950 I have only has 1 GiB memory (it cannot use the HD 6970 firmware) and I've set the clocks to 850/1350 (very mild overclock, I know), known to be stable for both MB, AP (no computation errors for, well, as long as I've had the card) and playing games. (Any higher causes freezing/lock-ups in games - I find games break before GPGPU get errors.)Soli Deo Gloria

I also tested the GTX 260 Core 216 today, just to see if there was any difference from Fermi/Kepler - I had a report typed up but then lost it all, but suffice it to say that the differences between r1316 and r1339 followed the pattern of the rest of my tests. Skipping the FFA pre-compute didn't change CPU time, but overall run-time increased by about 8%.

I used -ffa_block 2048 -ffa_block_fetch 1024. -ffa_block 8192 -ffa_block_fetch 4096 was very similar, but oddly enough, -ffa_block 4096 -ffa_block_fetch 2048 was consistently very slightly slower, but not by significant margin at all.Soli Deo Gloria

Hey guys, reading this thread sounds like a foreign language to me, but from what I gather, are we supposed to drop the binary into the setiathome.berkeley.edu directory, and in the app_info change the line:

<name>ap_6.01r557_SSE2_331_AVX.exe</name>

to

<name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe</name>

in the 2 places it is referenced?

I am just humbly trying to learn from you guys, but if I am wrong and there is actually a lot more to it than just that, I can wait for the next installer release and just do it the simple way without modifying the app info or anything?
btw, thanks for your hard work on these improvements.

Hey guys, reading this thread sounds like a foreign language to me, but from what I gather, are we supposed to drop the binary into the setiathome.berkeley.edu directory, and in the app_info change the line:

<name>ap_6.01r557_SSE2_331_AVX.exe</name>

to

<name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe</name>

in the 2 places it is referenced?

No, you don't want to do that, the SSE2_SSE2_331_AVX app is a CPU app, while the NV_r1316 app is a Nvidia GPU app.

You drop the files supplied into the project folder, and add the app_info section from the 2nd post of this thread into your own app_info, making sure you put it before the </app_info> closing tag.

Edit: and making one change: <type>cuda</type> should be <type>CUDA</type>

Hey guys, reading this thread sounds like a foreign language to me, but from what I gather, are we supposed to drop the binary into the setiathome.berkeley.edu directory, and in the app_info change the line:

<name>ap_6.01r557_SSE2_331_AVX.exe</name>

to

<name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe</name>

in the 2 places it is referenced?

I am just humbly trying to learn from you guys, but if I am wrong and there is actually a lot more to it than just that, I can wait for the next installer release and just do it the simple way without modifying the app info or anything?
btw, thanks for your hard work on these improvements.

Absolutely not.

Something called 'SSE2_331_AVX' is going to be a CPU app.

Something called 'OpenCL_NV' is going to be an NVidia GPU app.

If you have an older Astropulse NV GPU application specified, you could update that.

Otherwise, you would have to add the three elements which together (and inter-relatedly) specify the complete package:

<app>
<file_info>
<app_version>

You have to learn to 'read the chart' (to use your day-job terminology)

Will AV scan my computer tomorrow, SmartDoctor had turned the GPUs from
850MHz to 500MHz.? And wasn't fully started?
And a cmd screen was open and couldn't been closed.
This all 'happened' out of the blue?!
Had to change start-menu to take care about that.