The point you all are missing is the simplest one of all. And it was the original point ...
The point is that EaH should get no, I repeat *NO* time at all ... unless if, and only if, the primary project is down and the work buffer is empty. The whole point is to never do EaH unless it is absolutely needed. Like just before the computer goes idle. Your argument is that the share can be made small enough that it should not bother Raistmer (and all others that want this feature) ignoring the fact that they would not be asking for this feature if even that small of a fraction was not already too large for them. The point is to just do the primary project and only when the system is in dire need to do work for another project. Work fetch bugs are still present and the tendency of the system to over-fetch (which I have been reporting for a long time) means that using even extreme settings for RS can, and almost certainly will, cause BOINC to continually make mistakes and download work when it should not do so ... which means the users that don't want secondary projects to consume resources will continue to get more cycles than the user wants that project to have ... Back-up project is just that ... not a low share project, but a back-up only to the primary project ... On Jan 26, 2010, at 12:45 PM, Lynn W. Taylor wrote: > 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. _______________________________________________ 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.
