Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Completed Research Forum: Help Cure Muscular Dystrophy - Phase 2 Forum Thread: unit % progressing strangely |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 5
|
Author |
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: |
I have noticed that the current unit I am crunching seems to be going wrong.
----------------------------------------It was at 70% in 4 hours. Now it is 75% in 7 hours. Does this sound right? Patrick |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
HCMD2 process a bit differently than other WUs. Basically what happens is that if after 6 hours you are not 60% finished it will stop. If you are more than 60% it will continue until it finishes or you hit 12 hours, whichever comes first. The reason for this structure is that there are some "positions" which are very difficult to calculate and it sounds like you may have hit a couple of them in a row somtime after you passed the 60% marker. I wouldn't worry, just let it keep crunching.
----------------------------------------[Edit 1 times, last edit by Former Member at Jan 10, 2010 12:49:16 PM] |
||
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: |
Thought so.
----------------------------------------Currently 10hrs on 83% Patrick |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The progress you could see is (what I see on a 6.10 client)
----------------------------------------- If a 6 hour [first soft limit on run time] initial job, mostly parent tasks, they'll run to show 100% at the end of the 6th hour, and if internally reaching more than 60% of the positions, resetting to a percent of total positions. - If individual positions happen to run longer, the Time to Complete will increase. In this case 83% suggests that this job will cut off at the position that is underway at the end of the 12 hour [second hard limit on run time] I've had several parents just now that ran varying times, but completed all positions in the jobs through batch 289. For example: CMD2_ 0289-GRP75A.clustersOccur-2CL3_ A.clustersOccur_ 25_ 0-- 1112084 Valid 1/9/10 11:53:05 1/10/10 14:48:11 5.24 96.8 / 89.0 CMD2_ 0280-MAOMA.clustersOccur-2Z5X_ A.clustersOccur_ 45_ 164933_ 165829_ 1-- 95711 Pending Validation 1/9/10 09:36:18 1/10/10 14:30:50 7.03 75.8 / 0.0 CMD2_ 0280-MAOMA.clustersOccur-2Z5X_ A.clustersOccur_ 45_ 166727_ 167623_ 0-- 95711 Valid 1/9/10 09:36:18 1/10/10 11:02:27 7.37 79.4 / 66.7 CMD2_ 0289-GRP75A.clustersOccur-2EWY_ A.clustersOccur_ 262_ 1-- 1112084 Valid 1/9/10 11:53:05 1/10/10 07:24:36 3.56 65.8 / 60.8 CMD2_ 0289-GRP75A.clustersOccur-2ORK_ C.clustersOccur_ 53_ 1-- 1112084 Pending Validation 1/9/10 11:53:05 1/9/10 20:29:55 8.27 152.2 / 0.0 the 95711 is a slow duo centrino suggesting that work is lighter in this series. Question/Request: Any volunteers willing to write up the full rule book from observations, so we can paste it into the FAQ's? thanks
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All! |
||
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: |
Yes, unit stopped at time limit of 12hrs.
----------------------------------------Patrick |
||
|
|