Hopefully, this will get consolidated, put in a "cloud," and get done. The longer we wait for even our own NTPCkr the harder it gets to implement

As I was pressing the post button, I said "reset". Better yet, reinstall. I emptied the work queue and reinstalled just now. Now it is all ok.

Mostly OK. My passwords are now invalid. I was able to reset yours while writing this question, but the others were not so lucky. So it's off to another machine to try again. Could it be that you invalidate passwords if not used in X months?

I've forwarded this to the correct BOINC developer, let's see what he says back.
Is this all logged anywhere? In a continuous log?

As you can see in the Applications list there is only an OpenCL application for the Intel GPU for Astropulse on the Macintosh.
When you then look at the server status page you can see that at the moment no Astropulse is being split or sent out.

APs are usually only split when new 'tapes' are added. They are split from the same data that the Multibeam tasks are split from.

He is attempting to install Nvidia drivers so that he can run WU's on his GPU. I would follow the Nvidia driver install instructions for Linux. If possible d/l Nvidia drivers from a linux driver repository.

@Juan, I'm using HWMONITOR, both Nvidia and Intel will throttle down due to heat, i'm not worried.

AP CPU came in around 13.5 hours, I have 4 more crunching, my own estimated says 13.5 hours too.

Thanks everyone for all your help, I'm getting AP gpu/cpu, cuda tasks are more efficient too.

Throttling is something you want to avoid otherwise you'll start generating "exceed time limit" errors. ;-)

Cheers.

One tip: you must try to use the lunatics instaler, that will help you to configurate even better your host since you have a cuda5 GPU and a AVX capable CPU.

I installed lunatic, it changed the exe files for the tasks, but doesn't seem to have done anything except change cpu_usage for MB from .06 to .04. I was hoping to get AP, but none were downloaded. I went and changed app_info.xml count filed from 1 to .5, that's it.

When you install you select cuda5 and crunching ap on the nvidia?

You don´t need to change the app_info the app_config do the job for you.

One tip: you must try to use the lunatics instaler, that will help you to configurate even better your host since you have a cuda5 GPU and a AVX capable CPU.

I don't know how to do that, documentation doesn't explain it. There's only one app name setiathome_v7, so i can't have 2 configs, unless there's an undocumented syntax.

The basic file is:

<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.06</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_enhanced</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.06</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v6</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>1.00</cpu_usage>
</gpu_versions>
</app>
</app_config>

As you could see there are separete cpu_usage for each type of WU.

This file allow you to run 2 WU at a time on the GPU, if you want to run 3 just change the 0.5 for 0.33. But remember very few GPU´s can run 3 AP faster than 2. 3 MB i belive your GPU can handle, more no. Of couse YMMV, so you need to test.

BTW the diference of use 0.04 or 0.06 is meaningless in MB.

My "multiprocessors, use at most" setting was leaving 1 core free. But now I set cpu_usage to 1 and gpu_usage to 1 and mulitporcessor setting to 100%. This will make me run 15 cpu tasks and 1 gpu task.

Thats fine, works as expected, but i still belive 2 WU or maybe 3 on the GPU is the optimal setting,the 660TI is a very fast GPU, 1 sure not.
1 core is about 6.25% of your CPU (1/16 processors) so a number or 93% or 94%, I not remember if the rounding is up or down, will free the first core.
You could easely see what is the right one because when you free the core you will run 14 CPU task and 1 GPU task if is AP or 15 CPU + 1 GPU if is MB.

Oh, so that's why everyone sets cpu_usage to less than 1? What should I pick, 0.1, 0.01 or?

You use <cpu_usage>0.04 for MB, <cpu_usage>1.0 for AP. There are two diferent setting depending what type of WU you want to crunch. You could see that in the app_config file suplied.

If you only crunch MB you could use only the MB part of the file and use only 0.04 and leave only one core free for all the 2 or 3 WU crunching in the GPU.

Even in my hosts that not crunch AP i leave the file with both options enabled and choose what type of WU i want to crunch in the preferences page.