| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: Completion Dates Less than 10 Days |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 16
|
|
| Author |
|
|
rbotterb
Senior Cruncher United States Joined: Jul 21, 2005 Post Count: 401 Status: Offline Project Badges: 
|
One thing I occasionally get is new work packets that have a completion date that is only 5 days away rather than the standard 10 days. Since I don't always use my laptop enough some 5 day stretches of time to get in 6-8+ hours plus of usage to allow such packets to finish, I'm concerned that these short completion dates will just result in the work being done after the completion date and go to waste.
Is there any way to set up anything in the profile to keep this from happening? If not, it might be nice to add a flag for this situation so a user who has a lighter used computer can keep from getting these quick turnaround packets of work. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
There's some Berkeley development underway to differently rate "reliable". Getting these jobs with shorter deadline usually indicates and average result return of under 2 days, but the value does not decay when going off-line for a while or slowly.
----------------------------------------That said, a device profile option that is coupled to for instance laptops that irregularly are on travel duty, may indeed be something to consider for the techs. No trickery or reliance on complex formula... just straight up: No repairs/make up wanted [with initial default state of Yes rather than No] cheers
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 3010 Status: Offline Project Badges: 
|
rbotterb, these "short deadline WU's", are basically 'rework units' (i.e., they've either errored out, not been returned by their deadline, or are validation WU's to just check/confirm that a WU completed on someone else's machine does match with the verification WU (i.e., when a WU goes into an 'Inconclusive' status).
----------------------------------------As such, BOINC must believe that it can process the WU's in time - as, I'm led to believe that it does take into account the pattern your machine is available to crunch. To get into this "Reliable class", you've got to a) return a set number of Valid returns (and keep under that bar), and b) return WU's on a regular basis of under 2 days of being sent out. Now, as to how to drop out of this reliable class - the second option would probably be easiest - i.e., just set a WU cache up of 2.25 days.  |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
gb009761, that would not be advisable. His device would be off with > 2.25 days cache + work in progress for undetermined periods... more people waiting on quorum dependent wingman and if longer than 5 days, panic state on resume for the <on_frac> would be out of whack and rather than a single repair job expiring, more potentially would.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
PS:
----------------------------------------rbotterb, whilst an expired job may not feel to be good sitting on the resumé, it's no distaster. Many of these repair jobs actually have a due date before the wingman's job when pertaining to repairs. E.g Day 1 there is 2 copies send for an HCC job, both due day 10 Day 2 there was a crash for one of the copies. The repair job send out is due day 6 Day 6, the repair job expires as No Reply and another copy is send due day 10 Target quorum completion still day 10. Repair/Makeup have a 4 day deadline, requests for having them at least send out with the original deadline date on the list.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Apr 23, 2010 2:57:35 PM] |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 3010 Status: Offline Project Badges:
|
Sekerob, the reason why I suggested setting his cache to 2.25 days, was that, currently he must have been returning WU's in under 2 days so as to get on the "Reliable list" in the first place. Thus, I don't think another .25 days would result in many (if any) WU's being returned after the usual 10 day limit.
---------------------------------------- |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Think rbotterb will have to judge if comfortable with having a cache size that stops repair/make up jobs coming... he speaks of few hours daily so the cache would be sized to real hours, but if those hours are variable an over-cache state can develop, not either a Set and Forget situation.
----------------------------------------The No function request if considered for implementation will be many months away.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
rbotterb
Senior Cruncher United States Joined: Jul 21, 2005 Post Count: 401 Status: Offline Project Badges:
|
thanks for everyones input. I now understand what is going on with my situation. I'm more comfortable now just letting these short runs do their 5 day deal and if some of them don't make it - well there is that repair cycle to deal with it. I'll hang loose until that flag Berkeley is working on shows up in my profile and I'll set it accordingly when it becomes available. I happen to be between jobs now, so I do have times when I go a few days in a row being on my laptop for 4-8 hours a day posting on jobs and networking for new ones - so that is probably why I'm falling into this 'reliable' mode on my laptop nowadays - I guess there is some 'silver lining' of being out of work :-) Consider this posting solved and thanks for everyones input on this matter.
|
|||
|
||||
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
That said, a device profile option that is coupled to for instance laptops that irregularly are on travel duty, may indeed be something to consider for the techs. No trickery or reliance on complex formula... just straight up: No repairs/make up wanted [with initial default state of Yes rather than No] A "no repair"-option wouldn't really mean much, since projects can have a mix of "normal" 20-day deadline-work and "normal" 2-day deadline-work, so even with a 40% repair-deadline, the repair-deadline of original 20-day-work will be 8 days, and this is much larger than the "normal" deadline for 2-day-work. An user getting the work with 2-days deadline but not being eligible for the 8-day deadline-work would be the result of this...  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Of course Ingleside, as so many times, we need to underline for you that we're talking WCG [sec], 4 days standard for repairs/make-up, 10 days for regular and exceptionally 8 resp. 7 days for the A and B type of DDDT-2.
----------------------------------------The 20 days, with priority 10 is used to force the 8 day deadline distribution, they still only go to those with 2 day return history, FAICT. edit: So net, an website option at WCG, no repairs/make-up would, coupled to the priority >=10 not go to crunchers at WCG.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 2 times, last edit by Sekerob at Apr 24, 2010 2:30:20 PM] |
||
|
|
|