In Baseball, the hitter is supposed to hit the ball when thrown by the pitcher.
If the hitter misses, the catcher is supposed to catch the ball (to protect home base from a runner scoring). Behind the catcher, at a safe distance, is a backstop whose only job is to keep the ball from rolling very far away. It seems to me that the daily quota is a backstop -- it's to keep a broken host from running away with all the work. *If* that's the case, then I don't think this is an issue. It shouldn't ever happen in normal operation -- it should be far enough away on a healthy host that it does not interfere with play. Several have argued that a healthy host should not have an upper limit, and in the spirit of that idea, I would argue that the limit needs to be well above what that healthy host can do under the best conditions. The only other reason I can think of for a daily quota is for a project (like LHC) that has intermittent work, and wants to limit requests so that everyone has a chance to participate. -- Lynn On 6/2/2010 1:12 AM, Richard Haselgrove wrote: > I see that David has implemented the 'Reward for Validation' component of > this discussion (http://boinc.berkeley.edu/trac/changeset/21675). > > However, don't we need to do something about backoffs? > > At the moment, if you ever reach the daily quota, you get a message saying > typically "no work sent / reached daily quota of xxx tasks", and all > scheduler RPCs are inhibited until 'server midnight + rnd(1 hour)'. I assume > that's a server backoff instruction, and not coded into the client (which > wouldn't know the server's local time). > > But the daily quota is no longer a fixed value. Indeed, if you both reported > and requested work in the same RPC, your quota might be increased in the next > few seconds, as the work you've just reported starts to validate. The backoff > should be no more than the existing project RPC backoff and client 'no work > sent' exponential backoff. > > Unfortunately, at the moment I can't test any of this: we only have one test > project with this code, and it says > > s...@home Beta Test 02/06/2010 08:28:40 Reporting 26 completed tasks, not > requesting new tasks > s...@home Beta Test 02/06/2010 08:28:45 Scheduler request failed: HTTP > internal server error > _______________________________________________ > 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.
