AFAIK currently new quota mechanism supposes no upper limit for good host. If so, it should be chamged IMO. Upper quota limit still needed to protect project, but not from broken hosts, but from error in times estimation. If time estimated incorrectly (and on SETI it was plenty of times already, last example was yesterday), host will ask (and download) too much work. Cause actual host performance limited, to provide unlimited work to it will result in missed deadlines or massive user-cuased tasks aborts. Before last changes we had at least 1-2 days due to quota to be save from essentiannly infinite amount of work provided by server in case of error, now it's easely to allocate whole bandwidth to single host (until its harddrive will filled) if that host behaved good and had no quota resets for some time....
_______________________________________________ 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.
