I am having trouble reestablishing myself with lunatics.

What did you do (1, 2, 3, ...) so far?

Some errors seem to be server or network related.
The computer need restart
(I think there were video driver crash - those AstroPulse tasks that end in seconds with strange infinity values 'Single pulse: peak_power=1.#IO;')

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I should have been a bit more explicit. I have established myself with lunatics as far as the cpu wu's. Then I went to gpu's with astropulse and that worked, but then I thought I didn't want to use up an entire cpu thread with the astropulse wu like you had in your sample app_config so I changed over to using the gpu's for v7. And with all of these changes from the stock boinc/seti app to lunatics I had some problems and reset and the net of all of this is that I am not now getting my gpu wu's from seti. Which I guess they are holding back because of the problems I've had. Hope this is clear enough. Put in the good word for me with the management and tell them to send me my gpu wu's. :-)

When you did the lunatics install was it both the multibeams apps and astropulses or only the astropulses? If you didn't install the multibeams apps, you are going to have to go back and install them in order for you to get any MB v7s. But before you do that, save your app_config someplace just in case it gets delete when you install the apps. You might also want to post any event log info that might show why you aren't getting the GPU MB's.

Thank you! Thank you! Thank you! Everything is running now. Perfect. ET here we come!
I spoke too soon. I started getting my system crashes, so I took out msi afterburner and lunatics and put in the stock boinc (latest version). Then I couldn't get anymore gpu work. Then I took out my app_config file. Still can't get any gpu work. All of this leads me to think I need to stay with the stock app for boinc with catalyst ctl center controlling my overclocking, but I still have the current problem of not getting any gpu wu's. This is getting to be too much for my old retired brain cells and I'm sure you are getting tired of hearing from me.

Still can't get any gpu work.

The server keeps info for every app you run:
http://setiathome.berkeley.edu/host_app_versions.php?hostid=7304674

e.g.
SETI@home v7 (anonymous platform, ATI GPU)
Max tasks per day 1
Consecutive valid tasks 0

It takes a day I think for 'Max tasks per day' to be reset to 100 (?)
Every successfully done task (validated) multiplies by 2 the 'Max tasks per day'
2 4 8 16 32 64 (so you need a few good tasks to up the Max)

See my:
http://setiathome.berkeley.edu/host_app_versions.php?hostid=4832843

Then I went to gpu's with astropulse and that worked, but then I thought I didn't want to use up an entire cpu thread with the astropulse wu like you had in your sample app_config so I changed over to using the gpu's for v7

Wrong
Both AstroPulse and MultiBeam SETI@home v7 on ATI AMD "use up an entire cpu thread"

This is true when you use:
'new' Windows (>Windows XP) + 'new' ATI AMD drivers (>Catalyst 12.4 ?) + 'old' (current) ATI AMD apps
This (will) change with newer ATI AMD apps

(I don't need a free core because I use Windows XP + Catalyst 11.12)

Yesterday I tested (not in BOINC but in benchmark) the new (beta?):
AP6_win_x86_SSE2_OpenCL_ATI_r2180 but it fail on my system

I sent a PM to Raistmer with the log:
(still no answer, he must be busy or on vacation ;) )

" 
Error in ap oclFFT_1: -34
ERROR: OpenCL kernel/call 'clFFT_ExecuteInterleaved_ap' call failed (-34) in file ..\..\ap_science.cpp near line 2653.
Waiting 30 sec before restart...

The bin files generated:
AstroPulse_Kernels_r2180.cl_Turks.bin_V6_TWIN_FFA_CAL141646
AP_clFFTplan_Turks_32768_r2180.bin_CAL141646

OpenCL 1.1 AMD-APP (831.4)
(the AstroPulse_OpenCL_ATI_ReadMe.txt do not say what AMD-APP version is needed or I can't see it)


AP6_win_x86_SSE2_OpenCL_ATI_r1843 works OK

Windows XP
AMD ATI Radeon HD 6570 (NI TURKS) [ASUS EAH6570/DI/1GD3(LP)]
Catalyst 11.12

Full log:
http://pastebin.com/LtegsyGS
"

(the error is near the end of log)


P.S.
You probably are in the impression that SETI@home v7 do not need a free core because CUDA apps on NVIDIA do not need it

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

OK, everything is running properly now. I have lunatics reinstalled and the two gpu's are running fine. One thing I don't know is what to set the memory clock at when the core clock is set at say 650 MHz. Is there a certain % relation to the core clock speed?

I found out what the errors were when my win8.1 was system crashing. It's called a clock watchdog timeout. It has something to do with multi-core cpu's locking up. I got it again just now when I set my gpu's from 650 MHz up to 675 MHz and the memory clock from 667 MHz to it's limit (1,000?). The system did recover however without aborting all the unfinished gpu wu's, although some of them may have errors. I don't know.

Thanks to everybody for their help. Both gpu's are running and all of my seti is now under lunatics. This is one of the very best help groups that I have ever been associated with.

If I switch to astropulse for my gpu's, is it true that I have to allocate a full thread to EACH gpu? Like this, for example:


<name>astropulse_v6</name>


<gpu_versions>

<gpu_usage>1.0</gpu_usage>

<cpu_usage>1.0</cpu_usage>

</gpu_versions>

 
I don't think it's different from SETI@home v7 on ATI AMD

Use SetiPerformance to test (both SETI@home v7 and AstroPulse)
There is 'Cpu' drop-down box - select how many CPU tasks to run (in the test) concurrently with GPU tasks

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

If I switch to astropulse for my gpu's, is it true that I have to allocate a full thread to EACH gpu?

You don't have to but it helps to keep the GPU from being "starved" of a CPU to help it. It also as to do with what kind of chip you have. Intel (like yours) tend to be better at supporting the GPU than AMDs. I only AMDs chips so I always give each GPU a core to support it. That being said, you could play around with the ratios and found out what is best for you as far as time to completion. I play with mine for about 2 weeks till I finally just stayed at 1 core per 1 gpu for APs. My ratio of cpu to gpu for MBs is different from everyone else's because I found the sweet spot for my computer after those 2 weeks.


Happy Crunching..

Zalster

Thanks folks. Next question.
In using the stock lunatics for windows, version 0.41 I believe, it seems as though it is logically impossible to work only MB for the cpu and only astropulse for the gpu because if you select on the first page only cpu tasks for MB and not astropulse, then on page 2 you select both MB and astropulse tasks for the ati gpu, it won't work because you need a partial cpu for the astopulse tasks. If on page 1 you select both MB and astropulse for the cpu,then you get both of them running on your gpu AND your cpu.
Hope that wasn't too confusing.

I think you are asking if you can only run MBs on the CPU and APs on the GPUs right? I think it can be done. I think you have to modify your app_config so that you only run the MBs on the CPU and only run APs on the GPU. Removing certain sections is the first thing that comes to mind. I wish I could go into more detail but its Monday and its already been a full day and i've only been here 3 hours. Make a copy of you app_config and move it to another folder just incase something goes wrong. There maybe a way to do it with an app_info but i'm not sure. Hopefully one of the others will comment with instructions. I'll check back later when I find some time


Zalster

Yes that is what I am asking. This is my current app_config:
<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v6</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
</app_config>

Thanks for your time Zalster.

Hi Merle, (as always make a copy of both app_info and app_config and save it someplace other than the boinc folder just in case something goes wrong.)

Ok, I think it's the app_info that we will need to modify. You could remove the first section of the app_config

<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>

as this gives instruction on running MB on the GPU. In your app_info. I think we would need to remove the sections for running the astropulses on the CPU as well as the section dealing with MB on the GPUs. Hopefully it's not to long to post here. (sometimes they get mad when we made long post {but you didn't hear it from me}) ;) lol

Any comments from the peanut gallery???


Zalster

I left in that MB stuff in config_app because I didn't want to wind up without anything for my gpu in case the astropulse gpu wu's didn't come through.

Here is my app_info file but it looks too much for me to chance fooling with.
Thanks again.

<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_SSSE3x.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</name>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</name>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati5_cat132</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</name>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_sah</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
</app_info>

... it won't work because you need a partial cpu for the astopulse tasks.
.....
Hope that wasn't too confusing.

Yes, it is confusing for me.

I don't see a problem.
Just select only MultiBeam for CPU and only AstroPulse for ATI AMD
(I did just that and as you know I run this combination - MB CPU + AP ATI)

Only later you need to think if you need free cores.
Free cores can be done:
- constant free: in BOINC - Use XX% of the processors
- dynamic free: in app_config.xml - % CPU per running GPU task

If you use both 'constant' and 'dynamic' BOINC will do both, e.g.:
- 'Use 99% of the processors' will free 1 core at all times
- SUM the <cpu_usage> for all running GPU tasks
      The SUM is truncated (e.g. 2.9 cores = 2 cores free)

<cpu_usage>0.04</cpu_usage> will do absolutely nothing (you have to run 25 tasks * 0.04 for BOINC to act and free 1 core)

'constant' + 'dynamic' = total cores to free


P.S.
Do you know that (at the end of running) Lunatics' Installer creates new app_info.xml
(old files are moved to oldApp_backup)

* The above was edited during/after the next post by merle van osdol (so read again ;) ) *

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

OK. That is the answer I was hoping for.

As far as free cores. I want to run as fast as I can. The constant free I know about. I know Nothing about dynamic cores. I don't know how to figure what the amount (%) would be. If that SetiPerformance pgm is involved I can't figure out how it would be used. The last time I used that was to determine how many wu's a cpu core could handle most efficiently, but this is a different case. If I am wrong then I would need to see an example otherwise I can't see it.
Thanks.

I could put my question another way. Is the 0.04 of a cpu the optimal answer for running astropulse gpu wu's?

If that SetiPerformance pgm is involved I can't figure out how it would be used.

Involved in what?
It is only to test outside BOINC (no change to BOINC files/behaviour - but run it with BOINC exited)

Read again what I posted about 'Cpu' drop-down box
(use it to see how many CPU tasks you can run concurrently with GPU tasks without affecting GPU task times)

Is the 0.04 of a cpu the optimal ...

Read the edited post above.
Do a 'Cpu' drop-down box test in SetiPerformance

((as I posted already) people say 1.0 is needed on 'new' OS + 'new' driver + 'old' app - I don't have my own experience, I use 'old' OS/driver/app which don't need a free cores)

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)