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 |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello everyone,
I got a workunit here, which has got two valid duplications, and one detached. What is strange to me, is the fact, that in the result log of the valid duplications, the text is not the same in both duplication but one is Result Name: CMD2_ 1488-1NZW_ A.clustersOccur-1Z6T_ C.clustersOccur_ 25_ 1-- <core_client_version>6.10.17</core_client_version> <![CDATA[ <stderr_txt> INFO: Initializing Platform. INFO: No state to restore. Start from the beginning. Finishing early because max runtime has been exceeded.21619.723147 called boinc_finish </stderr_txt> ]]> whereas the other is Result Log Result Name: CMD2_ 1488-1NZW_ A.clustersOccur-1Z6T_ C.clustersOccur_ 25_ 2-- <core_client_version>6.10.17</core_client_version> <![CDATA[ <stderr_txt> INFO: Initializing Platform. INFO: No state to restore. Start from the beginning. called boinc_finish </stderr_txt> ]]> Why is the max. runtime exceeded and the result nevertheless is valid? How can I change the max. runtime? Is the result where the runtime has not been exceeded better than mine, where the runtime has been exceeded? What are possible reasons for exceeding max runtime? Thank you for any explanations. I just want to be sure, that my results are really ok. Martin Schnellinger |
||
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2982 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Martin, could you post the top level details of the WU in question - then things should be clearer
----------------------------------------![]() Basically though with HCMD2, each WU has an initial cut off limit of 6 hrs (providing that it hasn't reached 60% of it's estimated total calculations). If it's gone past 60%, then the WU will continue to a hopeful completion. If it's still not complete by the 12 hr mark, it's cut off at that point. In either case, if either of the wingmen are cut short, then a new WU is generated - with what's left of the WU still outstanding. Once we know how long each of the wingman's WU's took, then we'll have a clearer picture of what's happened. ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello, thank you for your first reply, and here is the top level info of the Workunit.
The WU took six hours and one minute on my machine (this is where the max. runtime has been exceed) On someone elses machine, it was detached and took zero minutesThen, after been detached here, it was sent to a third person, where it took 7 hours and 44 minutes. On the machine of a third person, in the end, Greetings Martin Workunit Status Project Name: Help Cure Muscular Dystrophy - Phase 2 Created: 10.02.11 Name: CMD2_1488-1NZW_A.clustersOccur-1Z6T_C.clustersOccur_25 Minimum Quorum: 2 Replication: 2 Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit CMD2_ 1488-1NZW_ A.clustersOccur-1Z6T_ C.clustersOccur_ 25_ 2-- 615 Valid 17.02.11 16:02:23 18.02.11 17:55:03 7.44 129.7 / 126.1 CMD2_ 1488-1NZW_ A.clustersOccur-1Z6T_ C.clustersOccur_ 25_ 1-- 615 Valid 13.02.11 13:33:39 14.02.11 18:12:32 6.01 59.0 / 60.8 CMD2_ 1488-1NZW_ A.clustersOccur-1Z6T_ C.clustersOccur_ 25_ 0-- - Detached 13.02.11 13:27:50 17.02.11 15:00:58 0.00 0.0 / 0.0 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
gb009761 described it exactly and succinctly. A pity that this pairing ended up of the longer running task, based on credit grant, to have done twice the work as the one hitting the 6 hours/60% soft stop. Essentially what was not done by the slowest in this quorum is resubmitted to a new quorum pair. The scientists require absolute match for all individual positions, a partial result validation not deemed acceptable.
--//-- |
||
|
|
![]() |