Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: New Beta Test - February 25, 2016 [ Issues Thread ] |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 91
|
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These babies are heading for 27-28 hours if extrapolating from 17% after 5. The fraction setting seems to work for this app, very exact TTC I'm getting if comparing client projections with the calculator output. That's going to be 3-4 hours longer than FAH2 on this machine ... No fanboy of the > natural day tasks. I've got one on a Core Solo laptop. It'll be days. |
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: |
3 of these on e5-2650v2 +linux mint
----------------------------------------each were suspended (laim off) near start. all now at 100% and still running (99.5+ cpu%) restarted 2 of them at this stage 1 now showing 66 checkpoints since The other showing 1 checkpoint since longest running is 16h 50m if they go beyond 18 hours in this state then what? Thoughts anyone? |
||
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
What's with the 18 hours? FAHB runs on average 24-26 hours on my I7-2670QM at 2Ghz. In 1:53 hours the already 1:03:47 days running HST will finish for a total of > 29 hrs, which is technically no problem. Frequent checkpointing is good, so no heavy management is needed to restart client or boot machine. It's a new science engine to WCG programmers, so they're on a learning curve.
----------------------------------------HST: Help Smash Tumors (an alternate name for HFCC-2) [Edit 1 times, last edit by SekeRob* at Feb 27, 2016 2:20:22 PM] |
||
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges: |
HST: Help Smash Tumors (an alternate name for HFCC-2) If so, they should go the whole nine yards, contact Marvel Comics to get a license and use Hulk Smash Tumors. That way, they could have a graphic of Hulk in the Simple view of BOINC Manager. |
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: |
OK so the two that were suspended during the 100% phase have now completed approximately 20 minutes after resuming
----------------------------------------I had turned on checkpoint debug after seeing these at 100% and still running observing the log messages shows that the 3rd and untouched wu completed 47 minutes afterwards. This processor running at 3.1 loaded First thoughts are that there may be a further runtime after hitting 100% and that that time could be a further hour depending on cpu speed I have another on a 2.4Ghz e5 cpu currently at 95% I shall observe more closely.... |
||
|
pvh513
Senior Cruncher Joined: Feb 26, 2011 Post Count: 260 Status: Offline Project Badges: |
When doing a suspend/resume cycle on one of these WUs, the completion percentage jumped up from well below 100% (roughly 80%) just before the suspend to 118% just after the resume. This could indicate that something is not reinitialized correctly when restarting from a checkpoint (apart from the fact that the progress calculation is obviously broken).
|
||
|
ca05065
Senior Cruncher Joined: Dec 4, 2007 Post Count: 325 Status: Offline Project Badges: |
Result Name: BETA_ HST1_ 000002_ 000829_ AC0010_ F00029_ S00001_ 0--
<core_client_version>7.6.9</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [07:33:13] INFO: Running initial simulatoin Writting checkpoint at step 580. [07:41:56] INFO: Completed step 1000 of initial simulation Writting checkpoint at step 1170. Writting checkpoint at step 1750. [07:50:30] INFO: Completed step 2000 of initial simulation . . . [21:36:50] INFO: Completed step 98000 of initial simulation Writting checkpoint at step 98540. [21:45:29] INFO: Completed step 99000 of initial simulation Writting checkpoint at step 99110. Writting checkpoint at step 99690. [21:54:07] INFO: Completed step 100000 of initial simulation Writting checkpoint at step 100000. [21:54:09] INFO: Finished initial simulation. [21:54:10] INFO: Running secondary simulation Writting checkpoint at step 1000. [22:02:39] INFO: Run complete, CPU time: 51256.749502 22:02:39 (19168): called boinc_finish(0) </stderr_txt> Note that the log in Results Status shows '[07:33:13] INFO: Running initial simulatoin' then '[21:54:10] INFO: Running secondary simulation' . Could this be the cause of continued running after 100% reached? |
||
|
pvh513
Senior Cruncher Joined: Feb 26, 2011 Post Count: 260 Status: Offline Project Badges: |
Note that the log in Results Status shows '[07:33:13] INFO: Running initial simulatoin' then '[21:54:10] INFO: Running secondary simulation' . Could this be the cause of continued running after 100% reached? No, the secondary simulation is very fast (10 min on my machine). The percentage completed went over 100% well before the initial simulation had finished... |
||
|
andgra
Senior Cruncher Sweden Joined: Mar 15, 2014 Post Count: 183 Status: Offline Project Badges: |
Had one run without any strange behaviour. Took 8.58 on a i5-3470/Win10 in parallel with 3 FAH2 tasks. Just waiting for my wingman now.
----------------------------------------
/andgra
|
||
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: |
The first of these newly finished HST's reached 100% in a cpu time of 18hrs 38m 27s
----------------------------------------The next reached 100% in a cpu time of 18h 50m 11s by the time both had finished the runtimes were 20h55m10s and 20h57m52s respectively so in each case they ran on for a further 2h 16m 52s I need this result from a wu that has not been suspended Edit: a third wu on this same machine ran on for a further 2h44m46s after reaching 100% in 21h47m48s and added 14 checkpoints in so doing. [Edit 2 times, last edit by OldChap at Feb 27, 2016 10:22:16 PM] |
||
|
|