Hi,

I am using Ras' optimised SSE3 and Cuda application, and i am getting lots of CUDA WU's sent to my machines, however, now i am not receiving any actual CPU WU's, no AP no nothing.

I don't know what has changed for this to happen, but i am now only receiving 6.03 CUDA units

Any ideas?

thanks

The production of Astropulse tasks is for the moment on halt. See Matt lebofsky's explanation here, which says amongst other things:

"The Astropulse splitters have been deliberately off for several reasons, including to allow SETI@home to catch up. We also may increase the dispersion measure analysis range which will vastly increase the scientific output of Astropulse while having the beneficial side effect of taking longer to process (and thus helping to reduce our bandwidth constraint woes). However, word on the street is that some optimizations have been uncovered which may speed Astropulse back up again. We shall see how this all plays out. I'm all for optimized code, even if that means bandwidth headaches."

---

thanks man

i thought i had done something wrong!

LOL, don't you always? ;-)

---

Well, I have the same problem but the answer doesn't apply:
I have a dualcore CPU and two GPUs. Both GPUs are running Seti@Home Cuda (I had to disable SLI for boinc to use both GPUs), but only one CPU core is running Astropulse, regardless of having two more Astropulse workunits ready for processing. I even updated my web preferences core limit from 2 to 4 (and then forced boing to read the new preferences) but I still have one lazy core.
Maybe it's because each CUDA is listed to use 1 GPU + 0.07 CPUs, which in total makes 1.14 CPUs so there is less than 1 CPU left, so boinc can assign a new task to it?!

---

Well, I have the same problem but the answer doesn't apply:
I have a dualcore CPU and two GPUs. Both GPUs are running Seti@Home Cuda (I had to disable SLI for boinc to use both GPUs), but only one CPU core is running Astropulse, regardless of having two more Astropulse workunits ready for processing. I even updated my web preferences core limit from 2 to 4 (and then forced boing to read the new preferences) but I still have one lazy core.

Hi,
You can try and add the cc_config.xml file to the Boinc data folder to get all the cores running.

---

Well, I have the same problem but the answer doesn't apply:
I have a dualcore CPU and two GPUs. Both GPUs are running Seti@Home Cuda (I had to disable SLI for boinc to use both GPUs), but only one CPU core is running Astropulse, regardless of having two more Astropulse workunits ready for processing. I even updated my web preferences core limit from 2 to 4 (and then forced boing to read the new preferences) but I still have one lazy core.

Hi,
You can try and add the cc_config.xml file to the Boinc data folder to get all the cores running.

Did the cc_config.xml thing and set the number of CPUs to 3. Now both my CPU cores and both my GPUs are processing at their full capacity. Thanks!
This kind of confirms that the problem lays in CUDA being assigned a fraction of a CPU, and since boinc sees less than 1 cpu left, it doesn't create a new process, no matter that there are 0.93 CPUs left.

---

Well, I have the same problem but the answer doesn't apply:
I have a dualcore CPU and two GPUs. Both GPUs are running Seti@Home Cuda (I had to disable SLI for boinc to use both GPUs), but only one CPU core is running Astropulse, regardless of having two more Astropulse workunits ready for processing. I even updated my web preferences core limit from 2 to 4 (and then forced boing to read the new preferences) but I still have one lazy core.

Hi,
You can try and add the cc_config.xml file to the Boinc data folder to get all the cores running.

Did the cc_config.xml thing and set the number of CPUs to 3. Now both my CPU cores and both my GPUs are processing at their full capacity. Thanks!
This kind of confirms that the problem lays in CUDA being assigned a fraction of a CPU, and since boinc sees less than 1 cpu left, it doesn't create a new process, no matter that there are 0.93 CPUs left.

Actually, the problem lies within BOINC's ability to schedule work for both CPUs and GPUs; and it has nothing to do with CUDA being assigned a "fraction" of a CPU.

What was actually happening, which I always prefer to explain before/while offering a solution, is that because of BOINC's aforementioned scheduling problem, the one CPU in your dual core was being used to feed the GPU, hence a fraction of it was being used. Since only CUDA can be crunched on the GPU, any time a GPU is crunching CUDA, no SETI MultiBeam tasks are allowed to be processes, leaving only AstroPulse available for the other core. If you did not have AP enabled in your account, the other core would have been idle while all the SETI MultiBeam tasks would have been waiting on the GPU to become free instead of falling back to the CPU while the GPU is in use.

There is a fix in the latest alpha release of BOINC, but it is not ready for public use yet.

---