• Suspend use of the GPU when certain programs are running, or on request from user.
  
• Allow SETI and Astropulse WU to run on GPU, or on CPU.
  
• More as I think of them.
  

ability to choose priority among projects, not the auto if i have 2 projects its 50/50, if 3 its 33/33/33.

workunit stats, number of workunits crunched sence XXX, configurable

ability to do as old boinc, "run as service, will run even if nobody is logged in"

• Run a non-cuda WU on the CPU that is partially used by a cuda process, in order to fully utilize that CPU.
  
  That is, if the cuda WU is using 15% of the time on one of the CPUs, then a non-cuda WU will be using the other 85% of capacity.
  
  
• Set processor affinity from BM (Boinc Manager) for each project or sub-project when more than one processor is available, with some priorities.
  
  For example:
  
  With a 4 CPU + 1 GPU system
  
  
  
  • Seti will run on CPU 3, and the GPU.
    
  • Astropulse will run on CPUs 1 and 2 as first priority.
    
  • Seti will run on CPUs 1 and 2 as second priority when there is no work for Astropulse.
    
  • Seti or some other project will run on CPU 0 when the computer is idle.
    
  • Suspend whatever was running on CPU 0 when the computer is not idle.
    

  
  

• Multiple projects can run at the same time when there are available processors.
  

• In order to keep all processors busy from a single pool of heterogeneous tasks including SETI@Home MB and AP WU, BOINC should be able to run any WU on a CPU or a GPU.
  
• Within BM, allow the user to configure which GPU(s) to use.
  

A couple of these would really be nice for a wish list:
NVIDIA Tesla C1060 Computing Processor
933 GFOPS / Card, lol. Drop the hammer and say goodbye.

Price: 	  $1,299.99

• Suspend use of the GPU when certain programs are running, or on request from user.
  

BOINC manager can do that! All you have to to is open one manager window per PC ;-)

Gruß,
Gundolf

BOINC manager can do that! All you have to to is open one manager window per PC ;-)

Gruß,
Gundolf

Oh wow, But not from one PC, Just from each PC, How unimaginative of You. :o

As Gundolf says, you can use one BOINC Manager window per remote computer. I run two BOINC Managers constantly, one looking at the localhost, one looking at my TV server. Just using remote_hosts.cfg and self-set passwords. Very easy.

<cc_config>
  <options>
     <exclusive_app>somegame.exe</exclusive_app>

<cc_config>
  <options>
     <nogpu_app>someUltra3Dgame.exe</nogpu_app>
     <limit_cpus_app>somegame.exe
     <n_gpu>1</n_gpu>
     <n_cpu>3</n_cpu>
     <use_gpu>xyzzy</use_gpu>
     </limit_cpus_app>
     . . .
  </options>
</cc_config>

The CUDA FAQ suggests using...

<cc_config>
  <options>
     <exclusive_app>somegame.exe</exclusive_app>

...to suspend BOINC when somegame.exe runs.

What is needed is a similar thing to make a distinction between the CPU and the GPU, something such as this:

<cc_config>
  <options>
     <nogpu_app>someUltra3Dgame.exe</nogpu_app>
     <limit_cpus_app>somegame.exe
     <n_gpu>1</n_gpu>
     <n_cpu>3</n_cpu>
     <use_gpu>xyzzy</use_gpu>
     </limit_cpus_app>
     . . .
  </options>
</cc_config>

...where <limit_cpus_app> will limit the number of CPU/GPU that BOINC can use when somegame.exe runs, <nogpu_app> will specify that BOINC can use no GPU when someUltra3Dgame.exe runs, and <use_gpu> specifies the address/id/slot number/what-have-you of the GPU to use when somegame.exe runs.

This will allow BOINC to continue running on the unused CPU(s) and GPU(s) (if any) while some game is using the other CPU and GPU.