It used to be the case that my normal Seti@Home tasks ran on my CPU(s) while Astropulse tasks ran on "0.128 CPUs + 1 ATI GPU". (I've got an AMD A8 3850 quad processor with built-in ATI GPU.)

Recently I've been receiving Seti@Home v7.7.03 tasks that claim to be running on 0.128 CPUs + 1 ATI GPU. These tasks all have either (opend_ati_cat132) or (opend_ati5_nocal) following their version number. v7.7.00 tasks are running on CPUs as normal and have nothing in brackets following their version number.

Is this all OK? And if I get more Astropules tasks will these take priority over the Seti@Home tasks on the GPU?

---

Graham Thomas

Is this all OK? And if I get more Astropules tasks will these take priority over the Seti@Home tasks on the GPU?

Boinc runs it's tasks in a FIFO (First In, First Out) order, when you get AP v7 tasks again, Boinc will run them when it's their turn. (unless they're in deadline trouble, then Boinc will do Wu's in deadline trouble first)

Claggy

There are CPU & GPU apps for SETI@home v7 & Astropulse v7. So everything is fine if you want to run both types on your CPU & GPU.
If not you can change your project preferences to only one type if you like, or you can use a cc_config.xml to exclude specific apps from your GPU.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Thanks to both of you. I'll (probably) let the scheduler sort itself out.

The progress bar and 'time remaining' indicators don't seem to work well with the v7.7.03 Seti@Home units that are running on the GPU. They don't appear to get done any faster than the others so I'm not sure that there's any advantage in running them in this way.

I'll see how things settle down and then decide whether to intervene.

---

Graham Thomas