I've seen "Milkyway@home N-Body Simulation with Orbit Fitting 1.87 (mt)" tasks complete in about 3 minutes (16 cores) or less sometimes. Now that I have all 32 threads running (AMD Ryzen 9 7950X3D), I have two 16 CPU tasks taking over an hour going at the same time. Is this a problem? Or do I just have new tasks that take longer normally?

I just switched back to using 50% CPU in settings to allow one task of 16 CPUs going, not two.

I'll watch and see how long tasks take at 50%.

What's the normal amount of time these tasks take, or do they vary?

Thanks,
Rich

Edit: It looks like I just switched at a time when processes take 50+ minutes for me to run. I've got one M@H N-Body Simulation with Orbit Fitting 1.87 (mt) [16 CPUs] going at 54% and 28 min ran, 23 minutes to go. I'll continue to watch, and switch back if it seems like they all run this way.

What's the normal amount of time these tasks take, or do they vary?

They vary quite a lot here, I have tasks, which take less than an hour of CPU-time while others take over a day (usually those with "data__9" in the name). For highest production I recommend running single thread tasks, i.e. set "Max # of threads for each MilkyWay@home task" to 1. Each task might run quite long than, but MT tasks are not very efficient, so you'll get more work done that way. For my Ryzen 5700G this is the difference I found between ST and MT tasks, you should get similar results.

---

Oh wow, that's counter-intuitive to me. nice hack!