Completed my first Task. It ran very fast - was on track for about an hour running with 2 MB 6.10 tasks at the same time, but exited early at the 35 minute mark with "Found 30 single pulses and 30 repeating pulses, exiting."

Please keep looking at outcome of this task. 30/30 exits, especially if they come first, are always suspicious it could be just noisy task, or some app failure.

Completed my first Task. It ran very fast - was on track for about an hour running with 2 MB 6.10 tasks at the same time, but exited early at the 35 minute mark with "Found 30 single pulses and 30 repeating pulses, exiting."

Please keep looking at outcome of this task. 30/30 exits, especially if they come first, are always suspicious it could be just noisy task, or some app failure.

Will do that. I started another task and will advise if anything is unusual. Glad we're starting to get some AP work. Thanks for the responses. Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Please keep looking at outcome of this task. 30/30 exits, especially if they come first, are always suspicious it could be just noisy task, or some app failure.

That first task, workunit 10249935008 has gone inconclusive. Another 30/30 exit, workunit 1024964421 has also gone inconclusive. Both are against the stock cpu app. Edit - both found 30/30 end edit. I've had 2 other 30/30 results, one of those validated against a stock cpu app. All 4 of the 30/30 exits came from ap_01jl10_aa_B5, so maybe its just a noisy file. Anyone else seeing this?

Have 4 results from 01jl11 that ran full length and are pending validation.Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Mike,
I don't know if it will hurt anything but I noticed one little problem with your NV app_info. You have this line... <name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe<app> It starts out as <name> and ends as <app> That should be changed to </name> shouldn't it?

Raistmer, I'm still using the old 560. Would it be okay to just change the name over to 1316 and leave the version number at 601 rather than 604 in the app_info? Is it necessary to ask for 604s?

Edit: to Mike, that mistake was made in your NV app_info example, I see now you have left the version name as 601 in your example for both. Is this working for you?

Mike,
I don't know if it will hurt anything but I noticed one little problem with your NV app_info. You have this line... <name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe<app> It starts out as <name> and ends as <app> That should be changed to </name> shouldn't it?

Raistmer, I'm still using the old 560. Would it be okay to just change the name over to 1316 and leave the version number at 601 rather than 604 in the app_info? Is it necessary to ask for 604s?

Edit: to Mike, that mistake was made in your NV app_info example, I see now you have left the version name as 601 in your example for both. Is this working for you?

How does this look it does not mention (it would be better to include libfftw3f-3.dll in app_info) and I changed <max_ncpus>0.2</max_ncpus> to <max_ncpus>0.04</max_ncpus> and
I changed <count>0.51</count> to <count>0.5</count>
Do I need to include <cmdline>-instances_per_device 1 -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -sbs 256</cmdline>

Okay, changed mine too and left it at 601. Also noticed that the old 560 was sse3 and the 1316 is sse2. Changed that also. Left everything else (unroll, ffa, ect) the same as I had it. Suspended a bunch of 603s to let a 601 start. Seemed to be running okay so I opened up the 603s again. It will be awhile before it restarts the 601 but it should be alright. I also changed my instances per to 2 and all my counts back to .5. My little GTS 450 should be able to handle it.

What are the default settings (values) for/of the application if nothing is in the <cmdline> in the app_info.xml file for...

-unroll
-ffa_block
-ffa_block_fetch

?

- - - - - - - - - -

How I could find/know which settings (& values) are the best for the own system for max. performance?

Thanks

unroll=2, ffa_block=1024, ffa_block_fetch=512 are defaults.

Usual method can be used - to try and to see.
There are some heuristics though I and others used before. They still work for this new build.
Can't mention all of those here but understanding what these params change should give insights how to use them.
So:
-unroll - changes number of data chnks processed at once in main loop. To loow number will leave some of GPU's compute units idle, too big can cause issues with stride of memory access (depends of GPU memory controller and number of channels it uses).
-ffa_block - how many different periods calculated on GPU at once. Each such period corresponds to OpenCL workitem. So again, if this value too low this can result in part of GPU being idle. Too big values have other issue - more and more unneeded work will be done cause data arrays for different periods have different sizes but GPU will process rectangular area corresponding to longest of arrays in block. Also, r1316 includes FFA pre-compute. It means that whole block will be redone if GPU found some signals inside (signals are rare so in most cases this result in faster operation than checking if there was signal or not after each small step). Too big block will reduce performance in case of signal (and usually each task has at least 2-3 signals).

Paul, the dll file goes in the SETI at Home folder. It doesn't need to be mentioned in the app_info.

Wrong Perryjay.

Regarding what to mention in app_info file: for stock users upgrading to this release it would be better to include libfftw3f-3.dll in app_info.
That's because stock version could mention it already. If you have this file in project dir then you need to mention it to save it from deletion. It's BOINC's paranoid "kill all I know" approach - quite useless cause nothing prevents to accumulate not known to BOINC trash in that folders.