| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Fight Childhood Cancer Project Forum
Thread: Very long running WU (Resolved) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have an unusual WU running - it is HFCC_t1_00932619_TrkB_0001_0. It has been running for 29 hours and To Completion is 48 hours.
----------------------------------------Usualy the HFCC WUs run some 8-10 hours. Another funny is that the Elapsed time on the Advanced view and the Simple view are very different (29 hours vs 11 hours) Any thoughts folks? [Edit 1 times, last edit by Former Member at Jun 18, 2009 6:19:03 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
In reverse order
----------------------------------------You're clearly on a 6.6 client, NOT recommended unless you do GPU computing as well. The developers had because of a timekeeping problem for GPU the phenomenal idea to drop CPU time in the Grid View and put wallclock time in place. If in that view and you hit the properties button after selecting the task you can see the CPU as well. 29 Hours wallclock versus 11 hours CPU time is not good. Means the job got only getting 38% of the CPU time. Suggest you exit BOINC and it's service completely and restart. Hopefully the job will run on. But, do watch the CPU time and the % progress. The wallclock is giving false information, particular when stuck or looping. Let us know how it goes
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jun 17, 2009 6:40:02 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the info Sekerob. I am on a 6.6 client, but have been for some time without any problems, so this latest has come as a surprise. The properties view is interestig, and shows CPU time 11 hours, Elapsd time 29 hours time remaining 46 hours, fraction done 27%. My preferences are set toallow 70% CPU usage. I will let the job run and watch it carefully.
Once again Thanks amigo. |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
WU completed successfully and vaildate after 18.32 hours CPU time (some 60hors elapsed time). the WU seemed to prgress faster after it got to about 60% completed).
Once again,many thanks for your support |
|||
|
||||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Good, if you please edit your opening post and insert [RESOLVED] in the title all other know there's an answer to the problem and case is closed.
----------------------------------------One note of curiosity, are you running 'crunch only when idle' on top of 70% CPU time (preference not ticked for Work while computer is in use)? That might explain the 18 hours CPU time versus 60 hours wallclock. cheers
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have specified 'use 70% of CPU', 'run while other work = yes', and 'on multi-processors use 100% of processors' - also 'run while on batteries = yes'.
All previous HFCC WUs had normal run times and CPU times - this was the first WU that I noticed because the run time was so long (estimated at 80 hours when it started). And, as I've said before, I have been running 6.6.28 since May 17 without any such 'problem'. The current WU for HFCC is showing Elapsed Time 6h, CPU time 4h, Est Time remaining= 16h - still a bit above what I would consider normal for HFCC. - But all seems OK - maybe just some longer running WUs |
||
|
|
|