Raistmer wrote: >> You'd be really angry if deadlines were missed.
> Well, what is wrong with this approach: rise low-share project priority only > if number of hours needed to complete downloaded task let say 1/2 or even > 1/3 of time remaining to deadline? > Hope you get the point - it should increase priority when it approaches to > deadline, not right after downloading. The problem is predicting the future. BOINC does not know how long work is going to take. It only has an estimate, and that could be off by quite a bit. BOINC knows that you've left the computer on for the past five days, but it doesn't know if you'll leave it on tomorrow. But the main reason is: if it does too much Einstein now, it can give that extra time back later by not downloading more Einstein. It can always make up later. If it doesn't do enough work to meet a deadline (if there are six hours of crunching left, and four hours to deadline), there is absolutely no chance of meeting the deadline, and work is at risk of being lost. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
