I'm running 4 projects: MilkyWay, Cosmology, Einstein and SETI. I just added MilkyWay a week or so ago. The MW GPU tasks appear to be running fine. The CPU tasks ("MilkyWay@Home N-Body Simulation 1.68 (mt)") aren't running at all.

BOINC shows (on the Tasks tab) a difference between MW and, e.g., Cosmology CPU tasks: Cosmology (whose CPU tasks run fine) shows "Ready to start (2 CPUs)" or "Running (2 CPUs)".

MilkyWay CPU tasks show "Ready to start (4 CPUs)". I'm wondering if the "4" is the cause of the problem. However, I can't find a way in any Preferences setting to reduce that to "2".

Any ideas?

Thanks.

the other projects probably have an earlier deadline? i have gpu work units that stop when i have cpu work units nearing the deadline.

I don't think that is it. One of the MW CPU tasks has been assigned to me since 6/22, another since 6/25. I've seen no evidence that any MW CPU task has ever run since I added the MilkyWay project.

I don't think that is it. One of the MW CPU tasks has been assigned to me since 6/22, another since 6/25. I've seen no evidence that any MW CPU task has ever run since I added the MilkyWay project.

The nbody tasks use multiple cpu cores to run, so if you have deadlines with the other projects that are too close then Boinc will not run MW tasks until they are in danger of not finishing in time. Once you do start the MW tasks though you may find they run and the other projects just sit idle for a bit. You might think about lowering your cache settings down to just a day or so it can switch back and forth quicker.