Milkyway@Home N-Body Simulation 1.4 (mt) (running 8 CPUS) uses only 70-75% of CPU even though preferences is set at 100%? Other single M@H tasks use 100% and other projects run at 100%.

Milkyway@Home N-Body Simulation 1.4 (mt) (running 8 CPUS) uses only 70-75% of CPU even though preferences is set at 100%? Other single M@H tasks use 100% and other projects run at 100%.

I has the same problem. Milkyway@home N-Body Simulation 1.76 (mt) (16 CPUs) uses only 4%-15% CPU. and it takes 8days to finish.. waste power

Thread bump.

Was this ever resolved, because I have the same problem.

It shows 8 days to finish something and is only using 17% of my cpu, even though I specified 75% as the max (i.e., 6 out of 8 for me).

The solution has been posted several times: set "Max # of threads for each MilkyWay@home task" to 1 in your MilkyWay@home preferences. Also make sure to allow BOINC to use 100% of CPU time.

---

Thread bump.

Was this ever resolved, because I have the same problem.

It shows 8 days to finish something and is only using 17% of my cpu, even though I specified 75% as the max (i.e., 6 out of 8 for me).

I doubt anyone is even looking at it.

Most projects that use multiple CPU will have a main loop that assigns work to each CPU and then waits for all to finish. There is some compute
overlap with multiple CPU, but not 100%. I have historically seen the Milkyway project not have real efficient multithreading.

I recently changed the NCPUs to 1 and the WU throughput increased dramatically along with CPU usage. If a WU has been computing a long time, I abort it.
That one CPU can finish several WU during the time it would sit there and not finish. Probably a bug in the threading logic.