Firstly it is best to post questions like this in the Number Crunching Forum.

I can only see your desktop machine attached to your account, however you should not worry as Astropulse work units should not normally be sent to Nvidia cards, this was a problem at the server end and has now been rectifed.

A GFX470 should not have problems with regular work units, laptops on the other hand do heat up quite easily. I have mine on a cooling pad, works a treat.

Bernie

Actually they have released a stock app for for both ATI/AMD and Nvidia. So yes you will be getting AP work unless you change your preferences.

After installing and running TThrottle type the Max temperature for CPU and GPU and check 'Auto Active'
This will Throttle processes running under BOINC when these Max temperatures are reached and keep them at that level.

Choose/type 'reasonable' Max temperatures - not too high, not too low
(good is 15-20°C under the Max allowed temperatures for CPU and GPU
e.g.:
if CPU is specified for 70°C Max allowed working temperature - type 55°C in the CPU box
if GPU is specified for 90°C Max allowed working temperature - type 70°C in the GPU box
)

"Why a donation?The program is absolutely free, but we like to improve TThrottle and supply you with signed drivers.
If you like our program, help us to continue our work.If you want to give us a donation the minimum amount is $1.
"

Need more AP... need more AP... need more AP! :) I have two ATI 5850's set to Xfire in my i7 950 box. They mow through the AP units in short order. Sometimes the GPU's are fully loaded 80% or better. On some AP units they run at between 12% ~ 20% or so, kind of odd. 90% of the time they are waiting to get their silicone on more units. Still both GPU's get AP WU, the i7 950 never gets AP WU... well done team!

Since there can only be about 3% as many Astropulse workunits as SETI@home workunits, it's had to catch very many. Astropulse also splits really fast compared to SETI@home. Check the server status page to see if any is actively being split. Once data files are listed as "done" it's less likely that you will get any. @SETIEric

Isn't it possible to cut down on the AP splitters so they don't finish long before the MB's are done?

what would that solve though? the project server only receives splittable AP data when Arecibo (or wherever it comes from) has data to send. and that data comprises only a minority of all SETI data that must be crunched (which is why there is approx. 1 AP task for every 20 or so Multibeam tasks). if the AP splitters are intentionally slowed down, we'll see AP work less often than we do now...

Isn't it possible to cut down on the AP splitters so they don't finish long before the MB's are done?

what would that solve though? the project server only receives splittable AP data when Arecibo (or wherever it comes from) has data to send. and that data comprises only a minority of all SETI data that must be crunched (which is why there is approx. 1 AP task for every 20 or so Multibeam tasks). if the AP splitters are intentionally slowed down, we'll see AP work less often than we do now...

The potential advantage of slowing down the AP splitters - perhaps by reducing the number of instances running at the same time - would be to even out the traffic flow on the download link. At the moment, it gets grossly oversaturated when AP is being split, and can be underutilised (though less often, nowadays) between AP batches.

I'm relatively new on BOINC (joined a few days ago), and I have a problem with OpenCL tasks.

I only got 1 OpenCL task (90 tasks in total for this computer) through BOINC. The server doesn't return any other OpenCL task for me, even if I force the refresh. The log event says "Scheduler request completed : got 0 new tasks".

It's frustrating, since my GPU computes 16 times faster than my CPU for MilkyWay@Home (05:47 for GPU versus 01:37:23 for CPU ). I own an AMD Radeon HD 7800 which support OpenCL 1.2, with Catalyst 12.8 (had nothing too for 12.6).

Any idea ?

Windows Version : 7 Professional x64
BOINC Manager version : 7.0.28

EDIT : nvm, just discovered the server status page. So no Astropulse task for the moment. Too bad :(

WTF o_o All the remaining time of my tasks are speeding up. I was at 3+ hours on a task (which is now computed with my GPU thanks to Lunatics), it ended in less than 3 minutes (fastest got computed in 02:10). It computes more than 60 times faster on my GPU, and at least 2 times faster on my CPU (one of the tasks is going at least 10 times faster). Tasks computed by the GPU are computed a lot faster than Astropulse tasks.

Something seems wrong. We are far away from the estimated 8x computing speed acceleration for the GPU. Even the CPU is computing at an insane rate. I guess I'll have to keep an eye on the "Invalid" page.

Anyway, thanks for the download link for this software. I'm impressed.

WTF o_o All the remaining time of my tasks are speeding up. I was at 3+ hours on a task (which is now computed with my GPU thanks to Lunatics), it ended in less than 3 minutes (fastest got computed in 02:10). It computes more than 60 times faster on my GPU, and at least 2 times faster on my CPU (one of the tasks is going at least 10 times faster). Tasks computed by the GPU are computed a lot faster than Astropulse tasks.

Something seems wrong. We are far away from the estimated 8x computing speed acceleration for the GPU. Even the CPU is computing at an insane rate. I guess I'll have to keep an eye on the "Invalid" page.

Anyway, thanks for the download link for this software. I'm impressed.

For this type of analysis, you need to compare apples with apples. Not all tasks have the same runtimes. Runtimes vary according to the angle range of the telescope at the time of recording. In addition, some tasks might exit early if they're very noisy - usually as a result of terrestrial interference.

WTF o_o All the remaining time of my tasks are speeding up. I was at 3+ hours on a task (which is now computed with my GPU thanks to Lunatics), it ended in less than 3 minutes (fastest got computed in 02:10). It computes more than 60 times faster on my GPU, and at least 2 times faster on my CPU (one of the tasks is going at least 10 times faster). Tasks computed by the GPU are computed a lot faster than Astropulse tasks.

Something seems wrong. We are far away from the estimated 8x computing speed acceleration for the GPU. Even the CPU is computing at an insane rate. I guess I'll have to keep an eye on the "Invalid" page.

Anyway, thanks for the download link for this software. I'm impressed.

For this type of analysis, you need to compare apples with apples. Not all tasks have the same runtimes. Runtimes vary according to the angle range of the telescope at the time of recording. In addition, some tasks might exit early if they're very noisy - usually as a result of terrestrial interference.

I agree that runtimes vary.

But I was talking about before and after Lunatics installation on my ATI computer. I had some tasks which just started when I installed it, and the remaining time changed. It went down. A lot. Tasks are computing faster. Even when computed by CPU, their computation time are 100% faster at least. And with GPU, it computes sometimes more than 6000% faster. That's why I'm impressed.

I have been having problems lately with GPU processing. AstroPulse v6 6.04 (ATI_opencl_100) has been causing error messages about my AMD video driver not responding and a restart being successful. It does this about every few minutes (all input locks up and the screen goes blank then slowly comes back. I am running 3 monitors but not displaying the SETI processing graph on any screen. Usually it only involves 2 monitors (connected to the graphics card - the other is connected via USB). Also the elapsed time resets to zero during these episodes. The other thing is that I do not have my local preferences set to use the GPU and Boinc is running one more task than my local preferences allow. It only does this when the above mentioned astropulse program is available. I will revisit my web specified options to see if I can turn off using the GPU. My video card is an AMD Radeon HD 6570. At first I thought I was having either video hardware or software problems but quickly narrowed it down to astropulse being the culprit.