I have Einstein running on my GPU. This uses "1 CPU + 1 AMD GPU". I also have Milkyway running on my quad core CPU. Often I get nbody tasks which are quad core. They use "4C". When both of these try to run at once, they don't. The GPU is stopped and does nothing, sitting there idle. I'd much prefer the GPU ran and stole some CPU cycles from the 4C task.
I thought about adjusting the Einstein tasks to say they only needed say 0.9C, but that would screw up in another situation. When Asteroids (4 of 1 core tasks) is running, and Einstein runs, it takes 1 of the 4 Asteroid tasks off, so there's a core free to assist the GPU Einstein task. I want that to still happen.
Is there a way I can tell Milkyway never to give me more than 3-core tasks?
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Copyright © 2024 Einstein@Home. All rights reserved.
You could try leaving the E@H
)
You could try leaving the E@H GPU tasks at 0.9 CPU, and setting your overall CPU usage to only 3.9 instead of 4 (this is a global boinc setting, not per project).
Unfortunately the boinc scheduler is rather stupid when it comes to tasks that need CPU and GPU to run and multi-core tasks, so there might not be anything you can do.
Ah, it's happened again and I
)
Ah, it's happened again and I think I was wrong to blame the 4 core Milkyway nbody. This time I have 4 1-core Milkyway modfits running on my quad core CPU, and nothing on the GPU, with only Einstein 1GPU+1CPU tasks queued. The reason being the modfits are on high priority as they're the second choice for the processor and were downloaded when Asteroids had no work left. I guess Boinc is making the most sensible choice after all, I think it always fills all cores and GPUs whenever possible, but if something has little deadline left, that has to come first.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.