When BOINC is first installed it'll get the Master file, then only asks 1 second worth of work. That's one task (per CPU?). I'm not sure if when you immediately increase the work request to 10 days worth of work, you actually get that? But if it is done this way, why not set the 1 second worth of work first request be the maximum per CPU/GPU, until that task is returned correctly, and only then allow for more work to be downloaded?
That way you won't get hosts that have BOINC just installed, download hundreds of tasks, then the user uninstalls BOINC (or downright deletes it) without that work ever returning. Can't you use the "reliable_hosts config" by default, where only those that are reliable get more than the default 100 tasks per day? Then you only need some safe keeping when such a reliable host starts returning bad work. The host needs to be dropped from the reliable hosts list at a given amount of bad work returned, but before it hits the daily quota. And it can only return to the reliable hosts list by returning good work for a set amount of days. Only after that time can it increase its work load again. -- -- Jord. _______________________________________________ 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.
