Once again, Milky Way is stuck on an N-VBody simulation for an hour and a half.
Progress remains at 73.24%, Elapsed time is 1:38: 17 and increasing while time remaining is 00:36:15 and increasing. If I left it alone, that could go on for days and days.

There have been several of these. When such a task is running, I notice that CoreTemp indicates a much lower temperature, like 114-120 degrees F instead of the normal range of 152-168 degrees. I guess the CPU is not active during those times?

When that happens, I just abort them.

Some n-body simulations don't do that, but run normally.

S, Gaber

Once again, Milky Way is stuck on an N-VBody simulation for an hour and a half.
Progress remains at 73.24%, Elapsed time is 1:38: 17 and increasing while time remaining is 00:36:15 and increasing. If I left it alone, that could go on for days and days.

There have been several of these. When such a task is running, I notice that CoreTemp indicates a much lower temperature, like 114-120 degrees F instead of the normal range of 152-168 degrees. I guess the CPU is not active during those times?

When that happens, I just abort them.

Some n-body simulations don't do that, but run normally.

S, Gaber

I have seen the same on other projects but never here. If you use Boinctasks you can get a much better picture of everything happening, including how much CPU each task is really using.

I too just abort anything that isn't being productive. Chances are it'll work on the next machine it's handed to. If it doesn't, the admin can see it has failed on all x machines the server tries.

When you see this happening a simple reboot will solve the issue.

---