| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: UD Windows Agent Support [Read Only]
Thread: Infinite loop ? |
| 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 |
Since 2 hours, i have a task going back from 33% to 32%.
Any info about this ? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
No matter, the task is now at 35%, sorry for the trouble
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The Microsoft minute strikes again!
Actually, I don't know how the progress is calculated. It quite possibly uses a heuristic in addition to fixed checkpoints. This would explain the re-evaluation you saw. |
||
|
|
GB033533
Senior Cruncher UK Joined: Dec 8, 2004 Post Count: 198 Status: Offline Project Badges: 
|
This 'loop' is something I've noticed on the last three tasks. They seem to reach a ceiling and then get stuck for a while. My current task reached 33.3% within 25 mins, but keeps rolling back to 31%, and has been doing it for over 35 mins. I'm sure it will eventually get past it, but it is strange.... any ideas why this is happening?
---------------------------------------- |
||
|
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: 
|
I suspect that Didactylos is correct.
----------------------------------------As each piece of the problem is completed, it looks at how many pieces it has done relative to the total number of pieces, how long it has taken and then projects the new expected time to completion and % done. This allow it to get more nearly accurate estimates as time passes (given that the pieces are more nearly similar than different). Clearly the whole thing is imprecise at best. Didactylos' used the word heuristic to explain this. |
||
|
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: 
|
The Microsoft minute strikes again! Actually, I don't know how the progress is calculated. It quite possibly uses a heuristic in addition to fixed checkpoints. This would explain the re-evaluation you saw. This is correct. We make an educated guess as to how many iterations a docking will take and base the percentage on that. However, some workunits take considerably longer than our guess and when the code reaches the guessed limit, it reevaluates the length and continues. That's why you see the percent oscillate a few percentage points near the end of the docking. You'll also notice the green line graph also gets reevaluated and you'll see the graph rescale accordingly. At the other end it's possible a docking takes less time than we predict and you'll see the percent jump a few percent. This is most noticable at the beginning of a workunit because we use this new information for predicting the length of subsequent dockings within the workunit. Rest assured the workunit is progressing just fine.
Rick Alther
Former World Community Grid Developer |
||
|
|
|