| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
MD-Crusher
Advanced Cruncher Joined: Jul 23, 2007 Post Count: 52 Status: Offline |
The below is an example where a repair job gets not even 2 days (20%) of the original 9 days it was due. This causes other project jobs to be unnecessarily pre-empted. Suggest for the rule to check the original due date and stick to it.
X0000050720310200506081318_ 2-- In Progress 01/05/2008 12:33:32 01/07/2008 07:45:32 0.00 0.0 / 0.0 X0000050720310200506081318_ 0-- Error 01/03/2008 17:36:44 01/05/2008 12:26:39 0.24 4.0 / 0.0 X0000050720310200506081318_ 1-- In Progress 01/03/2008 17:32:00 01/12/2008 17:32:00 0.00 0.0 / 0.0 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello MD-Crusher,
What status were the other results in the quorum on the Results Status page? It could make a difference. Lawrence |
||
|
|
MD-Crusher
Advanced Cruncher Joined: Jul 23, 2007 Post Count: 52 Status: Offline |
The top one is mine, 3rd in distribution and falls 5.5 days short in being due from the original set showing at bottom with the 12th. Now my copy has been returned and is waiting on the original.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello MD-Crusher,
It should wait till a checkpoint has been written before preempting. I don't know if that is actually happening. Well, the suggestion has been made. We'll let knreed mull it over. Lawrence |
||
|
|
|