| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: Odd WU parameters |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 206 Status: Offline Project Badges: 
|
I have about 40 WU's in the system at the moment on one PC - 8 have been halted and I have about 20 dated for return by 27 Nov, 12 for 26 Nov and the rest sooner (these have been halted - not by me) and 8 of those with a 27th return date are now being processed with High Priority.... I also see that there has also been a very marked increase in the time to completion column - out to 40 hours - the WU's are all being completed in about 3 hours.
----------------------------------------Has anyone else experienced either of these 'system changes' in the last 24 hours? Or is it just my PC that seems to be doing its own thing?  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
No change here.Running 5 PC's
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My guess: you're on BOINC 6.10.58 or thereabouts, you've recently processed some Beta workunits for which the duration prediction was greatly underestimated, so your Duration Correction Factor (Project tab -> Properties) is way above 1.0. That multiplies each task's duration prediction and causes BOINC to go into what we call panic mode.
Just let BOINC sort itself out. Each result completed will bring the DCF back down a bit. |
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 206 Status: Offline Project Badges:
|
I am running 6.10.58 and like many others have run Betas but that doesn't really explain why there is a sudden switch to run WU's with a return date 9 days away when there are others in the queue with earlier dates and 8 stopped WU's with return dates of 26th and one 19th!! This behaviour only started this morning (the last Beta ran through on Sat) - so why start High Priority working on Monday morning?? It doesn't seem very logical to me.....assuming logic applies of course!!!
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I assume that part of the algorithm/logic is that downloads not yet started will have their entire estimated duration multiplied by the DCF, giving the 40+ hours to complete, whereas the partially-processed tasks will have only their remaining duration multiplied by the DCF, giving a lower figure. BOINC then panics about the higher figures and switches tasks to run them at high priority.
I think BOINC 7.something avoids using client-side DCF. |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
... that doesn't really explain why there is a sudden switch to run WU's with a return date 9 days away when there are others in the queue with earlier dates and 8 stopped WU's with return dates of 26th and one 19th!! This behaviour only started this morning (the last Beta ran through on Sat) - so why start High Priority working on Monday morning?? The only new thing in this weird scheduling is that you hit it these last days.  The conditions are a rather large work queue and a sudden surge of the Duration Corrector Factor. Lots of WCG contributors have already experienced it in the past, particularly when running HCMD2 which had a very wide range of WU durations. This scheduling weirdness that most logical people consider as a bug is considered by its authors as a genial design improvement, which explains why it is still carried on from one release to the next one. Never mind... ---------------------------------------- [Edit 1 times, last edit by JmBoullier at Nov 18, 2013 4:39:04 PM] |
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 206 Status: Offline Project Badges:
|
After about 4 or 5 hours (and processing about a dozen or so WU's), there was a sudden reversion to 'normal service' and the halted WU's were restarted one by one - by the end of the work day, the times to completion were still between 28 and 40 hours for the 35/40 WU's in the stockpile (including newly downloaded ones) - but this strangeness only seems to have occurred on one of the PC's - none of the others 'caught the bug' - thanks for the comments guys - nice to know that there's someone out there!!!
---------------------------------------- |
||
|
|
|