Would it be possible to only give out Nbody for CPUs and not Seperation? Seems daft to do Seperation on CPUs when the GPUs are so much faster. There's not currently a way to choose Nbody only for CPUs if you have a GPU in the same system.

Hi, try this website project preferences.

Use CPU: Yes
Use NVidia and/or ATI GPU: Yes
N-Body: Yes
Separation: No
If no work for selected applications is available, accept work from other applications: Yes

CPU will be N-Body nearly all the time, unless server runs out of N-Body tasks.
GPU, with no N-Body GPU app, should get GPU tasks from Separation.

Hi, try this website project preferences.

Use CPU: Yes
Use NVidia and/or ATI GPU: Yes
N-Body: Yes
Separation: No
If no work for selected applications is available, accept work from other applications: Yes

CPU will be N-Body nearly all the time, unless server runs out of N-Body tasks.
GPU, with no N-Body GPU app, should get GPU tasks from Separation.

That's a good idea, I can't remember if I tried that before. In theory it should work. Have you tried this?

It still seems to be letting Seperation through to my CPUs. Perhaps if a computer asks for GPU and CPU work at once, and there's obviously no GPU Nbody, I get Seperation, but for both types of processor.

Some more settings on this would be much appreciated Tom!

Hi, try this website project preferences.

Use CPU: Yes
Use NVidia and/or ATI GPU: Yes
N-Body: Yes
Separation: No
If no work for selected applications is available, accept work from other applications: Yes

CPU will be N-Body nearly all the time, unless server runs out of N-Body tasks.
GPU, with no N-Body GPU app, should get GPU tasks from Separation.

That's a good idea, I can't remember if I tried that before. In theory it should work. Have you tried this?

Yes and it works great, I've been using it for years. I always setup the different venues at every project that has both cpu and gpu tasks and even use different resource share amounts for them too and then move my pc's to the different venues depending on my crunching for today.

Yes and it works great, I've been using it for years. I always setup the different venues at every project that has both cpu and gpu tasks and even use different resource share amounts for them too and then move my pc's to the different venues depending on my crunching for today.

Well it's not working for me, I'm still getting seperation on the CPUs.

Yes and it works great, I've been using it for years. I always setup the different venues at every project that has both cpu and gpu tasks and even use different resource share amounts for them too and then move my pc's to the different venues depending on my crunching for today.

Well it's not working for me, I'm still getting seperation on the CPUs.

these are the venue choices for MW:

Resource share 1
Use CPU
Use ATI GPU
Use NVIDIA GPU
Maximum CPU % for graphics
0...100 20
Run only the selected applications Milkyway@home N-Body Simulation: no
Milkyway@home Separation: yes
If no work for selected applications is available, accept work from other applications? no

So if you are doing BOTH cpu and gpu tasks here then there isn't currently a way to stop getting the wrong ones for your cpu. You can see there is no choice to NOT get nbody tasks for the cpu, you either get Nbody tasks or you don't. The same thing for the Separation tasks...you either get them or you don't and if you get them if you have both the cpu and gpu boxes above, sorry the boxes didn't actually come thru in my copy and paste, then you get tasks for both cpu's and gpu's.

these are the venue choices for MW:

Resource share 1
Use CPU
Use ATI GPU
Use NVIDIA GPU
Maximum CPU % for graphics
0...100 20
Run only the selected applications Milkyway@home N-Body Simulation: no
Milkyway@home Separation: yes
If no work for selected applications is available, accept work from other applications? no

So if you are doing BOTH cpu and gpu tasks here then there isn't currently a way to stop getting the wrong ones for your cpu. You can see there is no choice to NOT get nbody tasks for the cpu, you either get Nbody tasks or you don't.

But as sam6861 suggested, I've told it to only get Nbody, but get others if none available. So like he said, when asking for CPU work I should get Nbody. When asking for GPU work I can't get Nbody, so I get "accept work from other applications" which is Seperation. But the server doesn't seem to understand.

Tom! Please fix this!

So far, I got my CPU doing N-Body GPU separation with: The N-Body yes, Separation no, Accept work from other application Yes. BOINC 0.1 days of work.

Slow milkyway server and when requesting GPU and reporting tasks at the same time "Got 0 tasks", partially puts me off from reliably chrunching Milkyway tasks for weeks or months so I sometimes move on to other BOINC project servers.

Some other projects have faster servers and better configs like PrimeGrid have separate app selections for CPU, NVidia, AMD GPU, and can control number of threads per CPU tasks, all in their website project preference.

I've seen Peter asking about this a lot recently. I do think that it would be a good feature to add, but it's pretty far down on the list of things to do for the project. Sorry that it's annoying!

I've seen Peter asking about this a lot recently. I do think that it would be a good feature to add, but it's pretty far down on the list of things to do for the project. Sorry that it's annoying!

Fair enough, I guess you're quite busy. Easiest thing to do would be to not make seperation work for CPU at all. But I guess that might annoy some CPU-only folk....