Will n-body ever end? 1.64

Author	Message
Mani Send message Joined: 15 Jul 10 Posts: 3 Credit: 14,034,733 RAC: 455	Message 66543 - Posted: 18 Jul 2017, 1:27:11 UTC Hi! I have been running a 4 CPU n-body app for over two days now. It says that it has progressed 0.013%, which it has said since it started, and that it has 17414 days left to go. It is now 17 July 2017, the due date is 7/23/2017, and no other CPU task is being allowed to run. Will it ever end? Should I abort it? Should I just not run n-body apps? It is running on an AMD A10-7850K. ID: 66543 · Rating: 0 · rate: / Reply Quote

Mani Send message Joined: 15 Jul 10 Posts: 3 Credit: 14,034,733 RAC: 455	Message 66545 - Posted: 22 Jul 2017, 12:54:31 UTC Hi again! Since I have not gotten any advice as yet, and the deadline for the n-body app in question is only 36 hours away with 34008 days estimated left, I have aborted the job, aborted the other n-body jobs in the queue, and disallowed new n-body jobs. I have other Milkyway, non n-body, jobs which will miss their deadlines otherwise. ID: 66545 · Rating: 0 · rate: / Reply Quote

rbarker Send message Joined: 28 Mar 12 Posts: 1 Credit: 921,699 RAC: 0	Message 66546 - Posted: 27 Jul 2017, 23:42:41 UTC I've encountered this with n-body work units on occasion. Even though the estimated run time is 15-20 minutes, they sometimes tie up 4 CPUs for days. I abort them when I notice this and am inclined to not accept any more n-body work. Anybody else experience this? Anyone from development listening? ID: 66546 · Rating: 0 · rate: / Reply Quote

David Dewey Send message Joined: 3 Mar 09 Posts: 1 Credit: 48,348,684 RAC: 70	Message 66548 - Posted: 31 Jul 2017, 11:50:28 UTC - in response to Message 66546. I have been consistently experiencing the same problem. The 4 cpu n-body jobs were running fine up until a few months ago. I have also disallowed the n-body jobs. ID: 66548 · Rating: 0 · rate: / Reply Quote

Mr P Hucker Send message Joined: 5 Jul 11 Posts: 981 Credit: 375,690,881 RAC: 18,866	Message 66607 - Posted: 15 Sep 2017, 1:55:45 UTC - in response to Message 66548. They've always worked fine for me (on 4 completely different computers), although I may have started doing Milkyway after you experienced the problem. Maybe they fixed a bug? ID: 66607 · Rating: 0 · rate: / Reply Quote

Redirect Left Send message Joined: 8 Dec 12 Posts: 2 Credit: 54,992,805 RAC: 1	Message 66660 - Posted: 21 Sep 2017, 15:12:22 UTC Last modified: 21 Sep 2017, 15:12:42 UTC I'm having this error too. They start off with an estimated time of about 10 to 20 minutes, but when running, it quickly escalates to possibly 2-3 days. Until this is resolved, i've now disabled N-Body from running on my 2 systems. ID: 66660 · Rating: 0 · rate: / Reply Quote