Hi, returned to SETI@home after some absent time and very glad to see the CUDA support. What is really needed are seperate running options for the GPU and main system. ie:

Options for "Run on CPU when computer is active" seperate from "Run on GPU when computer is active".
And, "Run on GPU when Direct3D not active".
Plus options to never run on CPU or GPU, which would skip downloading those sections.

For the moment, I keep having to manually turn it on and off as I find the spikey CPU throttling to be quite irritating. More often than not, forgetting to restart it.

Regards,
Zek

Options for "Run on CPU when computer is active" seperate from "Run on GPU when computer is active".

Already available:
Seti global preferences, "Suspend GPU work while computer is in use? yes/no"

It's also available in BOINC Manager's local preferences (Advanced view->Advanced->Preferences->Processor usage->"Use GPU while computer is in use".

And, "Run on GPU when Direct3D not active".

With DirectX always running this isn't possible. Any and all Direct3D drivers are always loaded.

But code has been added for BOINC 6.10 that will check against the Nvidia API if something else 3D intensive is already using the GPU. If something is, CUDA won't be used at that time.

Plus options to never run on CPU or GPU, which would skip downloading those sections.

Also already available.
Seti@Home project preferences:
- Use Graphics Processing Unit (GPU) if available yes/no
- Use Central Processing Unit (CPU) yes/no

---

Options for "Run on CPU when computer is active" seperate from "Run on GPU when computer is active".

Already available:
Seti global preferences, "Suspend GPU work while computer is in use? yes/no"

Yes, saw those options. I'm saying suspend CPU work while computer in use. But keep GPU work running.

But code has been added for BOINC 6.10 that will check against the Nvidia API if something else 3D intensive is already using the GPU. If something is, CUDA won't be used at that time.

That would be ideal yes.

Plus options to never run on CPU or GPU, which would skip downloading those sections.

Also already available.
Seti@Home project preferences:
- Use Graphics Processing Unit (GPU) if available yes/no
- Use Central Processing Unit (CPU) yes/no

Ok, was looking for options in BOINC for these. Very roundabout way of doing things if you want to suspend CPU work.

Seti global preferences, "Suspend GPU work while computer is in use? yes/no"

Yes, saw those options. I'm saying suspend CPU work while computer in use. But keep GPU work running.

The one above it is used for that: "Suspend work while computer is in use? yes/no".

Ok, was looking for options in BOINC for these. Very roundabout way of doing things if you want to suspend CPU work.

That's because they are project preferences, not BOINC preferences.
CUDA (and in a bit CAL) are new-comers, added on later. Before that BOINC was using the CPU, so it's very counter-intuitive to have a BOINC (own) preference not to use the CPU.

---

Seti global preferences, "Suspend GPU work while computer is in use? yes/no"

Yes, saw those options. I'm saying suspend CPU work while computer in use. But keep GPU work running.

The one above it is used for that: "Suspend work while computer is in use? yes/no".

Well, that's largely my point. I don't need it to suspend all work while computer in use. Just the CPU work, keeping GPU alive.

But as you say, perhaps when the newer CUDA system has matured for longer. I understand fully how growing applications don't quite turn out the same as fresh ones.

Thanks for your time.

There are only a handful of projects with CUDA applications. Most of the 75+ projects still use CPU applications, which makes it really a bad option to have a BOINC preference for not using the CPU. People are forgetful enough as it is, but they're oh so quick to jump onto forums (these and project forums) to blame something in BOINC is broken over a preference they themselves set and forgot about.

Hence that the CPU disabling preference is project based.

---

There are only a handful of projects with CUDA applications. Most of the 75+ projects still use CPU applications, which makes it really a bad option to have a BOINC preference for not using the CPU. People are forgetful enough as it is, but they're oh so quick to jump onto forums (these and project forums) to blame something in BOINC is broken over a preference they themselves set and forgot about.

Hence that the CPU disabling preference is project based.

Isn't the project-level CPU on/off switch actually a task allocation control (send/don't send work intended for CPU processing), rather than a 'suspend while in use' switch, where we currently have 'suspend BOINC entirely' or 'suspend GPU only', but not 'suspend CPU only'?