Crunching overdue WUs
18 Sep 2006 13:16:27 UTC
Topic 191842
(moderation:
Hello fellow-crunchers!
Due to a crash a while ago, I lost WUs for about a week. A couple of days ago, they were resent. Unfortunately I couldn't keep track of those for the weekend, but apparently I was crunching WUs of which the deadline was already passed...
Is there no check in BOINC that overdue WUs will not be crunched?
Due to technical difficulties, I usually run Linux command line only. Is there a way to see those deadlines from command line? The boinc client can extract them from the client_state.xml, so it should be possible...
Thanks in advance!
Bert
Somnio ergo sum
Crunching overdue WUs
)
There is no check because there are a couple of projects that accept the data even thought it's late. CPDN is one of them. Actually most do, if you still get it in before the new result that was sent out comes back.
RE: There is no check
)
Thanks PoohBear for the explanation. I'll just keep it in mind next time it happens.
I aborted several already so that I can meet the deadline again. I think it's a waste of resources to compete with another computer for the credits. After all, it's the result that counts for the project.
Regards,
Bert
Somnio ergo sum
RE: I aborted several
)
Actually you don't have to abort reults before you see on WU page that it had been issued once more time to another host. Of course scheduller will issue the same WU to another host if your host gets late. But this won't be done immediately but rather after a few hours. So if your host manages to finish the result, upload it and report it, this might mean that another user won't have to crunch it.
However, if your host fell behind by more than a few hours, then it's perhaps the best to abort those results.
Metod ...
I had the same with HashClash
)
I had the same with HashClash a couple of days ago (I attached and it promptly overcommited my computer so badly I fell behind) and I aborted all those as well- after letting the PC on 24/7 trying to get as many WUs as possible done before the deadline.
Unfortunately I had to give
)
Unfortunately I had to give it up. My computer crunched the WUs in time, but did not report them (although I've set "Connect to network about every" 0.05 days a while ago). So they were too late any way. Again, the computer crunched for nothing last night :(
Thanks for the replies anyway!
Happy crunching,
BS
Somnio ergo sum
Yeah, I know that prob ^^ and
)
Yeah, I know that prob ^^ and I actually got up at night to check ;-)
Annika wrote: RE: Yeah,
)
Annika wrote:
Really?
Now that's what i call dedication! :-)
Alex.
"I am tired of all this sort of thing called science here... We have spent
millions in that sort of thing for the last few years, and it is time it
should be stopped."
-- Simon Cameron, U.S. Senator, on the Smithsonian Institute, 1901.
Yep. Wouldn't have been
)
Yep. Wouldn't have been necessary, though, they had already uploaded allright.
RE: Unfortunately I had to
)
The part I'm not understanding here is why your machine is showing a 7 day deadline for the run of WU's which went overdue, while the other hosts apparently got the full 2 weeks.
I can only speculate something went wrong on the backend.
Alinator
RE: The part I'm not
)
I think the clue is in Bert's first post, where he says the WUs were lost and then resent.
AFAIK, when a WU is resent, it retains the original deadline it was given when it was sent the first time.