| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Conquer Cancer
Thread: 2 and 3 minute work units??? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
David_L6
Senior Cruncher USA Joined: Aug 24, 2006 Post Count: 296 Status: Offline Project Badges: 
|
I have some work units waiting to run that show 2 to 3 minutes remaining. ???
---------------------------------------- |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Are they beta? Or have you just run some beta work?
See the beta forum for more details - the incorrect time estimates on the beta units are going to mess with the estimates for other projects, too. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Possible, BOINC is indiscriminate both when it is in deadline jeopardy and when on time slicing.... it will switch even on the last checkpoint even when there is still some wrap-up work to do. Have proposed one time to let a task finish when it is say within 5-10 minutes of completion or an X percent.... something for a far away future, maybe.
----------------------------------------That said, some older clients suffered from prematures.... not seen job flopping on multiple tasks with identical deadline for a while and certainly not on 5.10.30 and above (when there are deadline issues). [edit: and yes if beta, follow post above]
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Apr 17, 2008 11:51:31 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Possible, BOINC is indiscriminate both when it is in deadline jeopardy and when on time slicing.... it will switch even on the last checkpoint even when there is still some wrap-up work to do. ...has been my favourite topic while being low on RAM and SWAP some time ago  That said, some older clients suffered from prematures.... not seen job flopping on multiple tasks with identical deadline for a while and certainly not on 5.10.30 and above (when there are deadline issues). Most recently two hours ago, a HCC1 5.20 task has been preempted on nearly 100% after 5:31 hours and when started again, finished in under 3 minutes. Windows Boinc 5.10.45. Not an older clients' issue. As said multiple times, it is happening (sort of) deterministically, if aditional projects are run along WCG and an app checkpoints while finishing. If the tasks' deadlines are far enough, then they do not really matter. And it (the job flopping) is probably not to change (on both client and app sides) in the near future. Or as Sekerob noted: "...something for a far away future, maybe". [Edit 1 times, last edit by Former Member at Apr 17, 2008 2:02:47 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The key is in the last few word you quoted "when there are deadline issues". There are not therefore most of this 'last minutes' would get resolved simply by forcing a completion when at or near end. It's more efficient on memory, more efficient on performance.... I'm reasonably convinced of that.
----------------------------------------Until then, it has nothing to do with the job flopping / deadline events. That was remedied properly quite some iterative versions ago. I just mentioned that as a matter of historic reference.... maybe should have left it off, not to confuse. ciao
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The key is in the last few word you quoted "when there are deadline issues". There are not therefore most of this 'last minutes' would get resolved simply by forcing a completion when at or near end. It's more efficient on memory, more efficient on performance.... I'm reasonably convinced of that. ciao Not all projects are as good at estimating the time remaining as WCG. So it was decided not to put any kind of "finish it if it is close" logic into the client. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Actual it could, similar to whether the science wrapper is told to check or not check if permitted to write checkpointing (Primegrid, QMC, Proteins@H are not doing it). Include an upfront hook to tell the client that it is nearing the end. Each project can set it or not.
----------------------------------------Now, who decided that? Is there some trac ticket discussion to follow the logic why it is not practical?
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|