As a reminder, there's no such thing as CPU workunits and GPU workunits; they're all the same. Workunits are not assigned to a specific resources until BOINC requests more on your local machine. So if you're not getting work for a specific resource, it is always related to work fetch on your local machine.

As a reminder, there's no such thing as CPU workunits and GPU workunits; they're all the same. Workunits are not assigned to a specific resources until BOINC requests more on your local machine.

The one exception are VLAR WUs on NVidia GPUs. Earlier video cards had issues with them, so they are blocked from going to all NVidia GPUs. When there are a lot of VLARs about, it's not unusual to get
No tasks sent
No tasks are available for SETI@home v7
This computer has reached a limit on tasks in progress

or

Project has no tasks available

responses when requesting GPU work, even though the CPU requests result in getting work. Eventually there will be enough non VLAR work available for the GPU & you'll get a whole bunch in one hit.

---

Grant
Darwin NT

As a reminder, there's no such thing as CPU workunits and GPU workunits; they're all the same. Workunits are not assigned to a specific resources until BOINC requests more on your local machine.

The one exception are VLAR WUs on NVidia GPUs.

And AMD/ATI GPUs, And Intel GPUs.

Claggy