Questions and Answers :
Wish list :
Request to kill WU's that deadline has expired
Message board moderation
Author | Message |
---|---|
Andrew Waddington Send message Joined: 1 Jun 99 Posts: 69 Credit: 55,557 RAC: 0 |
Rom Just spotted this item in the taskbase database: Preemptive scheduler should consider report deadlines when determining preemption. I would like to add to this request with the following, when a report deadline has passed the the WU is killed by the BOINC Core Client and move on to the next WU in the current project timeslice. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
|
Andrew Waddington Send message Joined: 1 Jun 99 Posts: 69 Credit: 55,557 RAC: 0 |
> If it is almost done, why not finish it and take a chance. If it is not > started, BOINC should kill it and wait for another. This leaves a gray area > about the meaning of "almost done". My thought was to kill the WU only after the deadline has passed, so if the WU time to completion indicates that it can not be completed before the deadline, continue to process it just in case it does finish and you still get the credit for the work done. That should get rid of the gray area of almost done. |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
On wu that haven't started yet, no problem to ditch them then passed the deadline. But it doesn't make much sense example to ditch a CPDN-wu if got 10 hours expected left to crunch then passing the deadline... The same will hold in projects like seti@home with their short wu, since if the pre-emption is fixed to take into consideration the deadline, the result will at most be returned a couple of hours after the deadline. Since most users is using atleast 1 days cache this will be longer to wait on than someone missing the deadline with a couple of hours. |
Andrew Waddington Send message Joined: 1 Jun 99 Posts: 69 Credit: 55,557 RAC: 0 |
Correct me if i'm wrong but once a deadline has passed your result is allowed to be uploaded and reported but is not used in the validation process, so whould it not be better to move on and process other unexpired WU's instead of data that will not be used. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
> Correct me if i'm wrong but once a deadline has passed your result is allowed > to be uploaded and reported but is not used in the validation process, so > whould it not be better to move on and process other unexpired WU's instead of > data that will not be used. Your result will count if it is returned and validated before the replacement is returned and validated. The replacement will count no matter what. This is the one way to get more than 3 verified results for a single WU. If the project is down, it is possible that you could crunch the unstarted WUs before the project got back up, report the WUs, and the server would not even get around to sending them back out again. |
Andrew Waddington Send message Joined: 1 Jun 99 Posts: 69 Credit: 55,557 RAC: 0 |
So a deadline is really a dyingline, and so we go back to your comment about the grey area |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.