| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: deadlines way too short |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 28
|
|
| Author |
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges: 
|
I just downloaded an 8 hour WU, that the deadline is only 6 hours out. I aborted it because there was no point since it would be late. See for yourself here. Everyone was allowed only 6 hours to crunch this.
----------------------------------------http://homepage.mac.com/zombie67/WU.png It may take a little while for this link to start working. .Mac seems to be unavailable at the moment. I have another one with the same problem on another machine.  |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
hi zombie 67,
----------------------------------------Normally all other work is stopped for a rush job like a Beta and even though the deadline does seem very short, by the time the system realises yours is not back, the work unit on your machine is already 3/4 way. When yours comes back, it would stop the sending of the next and the next as a result of ever repeating 'No Reply' knreed posted that they were looking for the data, and the more the better, so suggest you just crunch it. If there were a points issue, it can be resolved later, but the most important thing is to get completed or even erred jobs back. thanks for testing cheers
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jun 23, 2007 6:27:45 AM] |
||
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges:
|
I think my point wasn't clear. There was no time to return the results. 6 hours allowed for an 8 hour job. If the project is going to issue 8 hours of work, the deadline should be set to at least 8 hours.
----------------------------------------Edit: This not a slow machine. it's a 3.2ghz Xeon Edit #2: It sounds like the project is trying to force EDF (panic mode) in BOINC, in order to put this work to the front of the queue. Anything with a deadline of 24 hours or less will do it. No need to set it so short results are returned past deadline. http://boinc-wiki.ath.cx/Earliest_Deadline_First [Edit 3 times, last edit by zombie67 at Jun 23, 2007 6:48:38 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Yes your point was clear, and by crunching it, you would stop that 'No Reply' cycle after the next 6 hours.... remember, these times projected at start are only estimates of a new batch.... in actuality they could go much faster! Get jobs regularly with inflated estimates like 12 hours and done in 6 or 7. It settles as BOINC learns.
----------------------------------------The 'panic' only lasts as long as the beta job is ongoing.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges:
|
Yes your point was clear, and by crunching it, you would stop that 'No Reply' cycle after the next 6 hours.... remember, these times projected at start are only estimates of a new batch.... in actuality they could go much faster! Get jobs regularly with inflated estimates like 12 hours and done in 6 or 7. It settles as BOINC learns. The 'panic' only lasts as long as the beta job is ongoing. I'm not sure what you are trying to say here. I understand how BOINC works. I just don't see the point in setting an unreasonable deadline. 6 hour and 24 hours will provide the same result as far as prioritizing the work. So why not set it higher and allow 1) work to be returned on time, avoiding unnecessary work by the project to manually award points and 2) prevent scenarios where people like me see wasted crunching going on, and aborting tasks I am not seeing the upside of deadlines that are shorter than 24 hours. [Edit 1 times, last edit by zombie67 at Jun 23, 2007 7:13:35 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
No one disagrees that 6 hours is unreasonable and 12 or 18 or 23 hours would have been fine to get priority too, it's just that if you crunch on, you will be the one breaking the vicious cycle i.e. stop the perpetuated 6 hour 'no reply'.... this is a beta test and no one is going to bite if a job comes back late.
----------------------------------------Added: There's a funny here in that the 5.10 client gives priority to short jobs over long jobs.... maybe the techs had that in mind.... guessing.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jun 23, 2007 7:26:42 AM] |
||
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges:
|
No one disagrees that 6 hours is unreasonable and 12 or 18 or 23 hours would have been fine to get priority too, it's just that if you crunch on, you will be the one breaking the vicious cycle i.e. stop the perpetuated 6 hour 'no reply'.... this is a beta test and no one is going to bite if a job comes back late. I feel like we are talking in circles. Yes, I am already on board with the beta. No need to seduce me. I'm trying to fix the logistics, and the unintended consequences. What I don't understand is why I am getting back "don't worry about it", instead of "good point, i'll forward your feedback to the project". I am not attacking the project here. There is no need to drop into defense mode. Added: There's a funny here in that the 5.10 client gives priority to short jobs over long jobs.... maybe the techs had that in mind.... guessing. I hadn't heard that one, about the prioritization. Where can I read more about it? |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
There is no documentation i know off on the short over long jobs rule, just observed during testing of the 5.10.x clients and just know the whole scheduling module had a very major overhaul (5.10.7 is still not recommended by WCG for production)
----------------------------------------I don't know from where you are, but the thanks for reporting is a given.... and recommending to let it run. CA's forward many things to the technicians.... I don't always acknowledge that as it is sort of automatic, but good point to add that comment (was i defensive now ;>). Anyway, as we hopefully now have gone full circle, have a great day ciao
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
kh6dc@arrl.net
Advanced Cruncher Joined: Dec 5, 2006 Post Count: 69 Status: Offline Project Badges: 
|
Sekerob, I had to abort 4 times since the deadlines had passed on my 2 crunching machines. Will let it go from now on, even past the deadlines.
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Just to confirm, an alert was placed in the back-room forum.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|