First of all, it doesn't account for GPU presence. + Setted limit too low. For few weeks already we see regular problems with result uploading @ SETI project. Currently project in such situation again. It's problems with servers, not with participants computers or connections. That is, as soon as server will be repaired (most probably, just rebooted), all tasks will be uploaded almost immediately. It's well known situation cause it occured many times already. Moreover, project still provides new work for download. But users hosts can't download new work because of this BOINC's "feature" Who affected most of all: peoples with low cache values (btw, it's default settings! ) and peoples with fast GPUs (they can't use many days cache because of another BOINC well known limitations).
This feature should prevent situation when participant's host not able to return work because of problems on client size, not project-wide problems on server side. So I propose to increase outstanding uploads threshold _considerably_. It will help not to lose performance during short-term server-side problems, but still will serve main purpose of this feature - will ultimately prevent new task downloading by hosts w/o ability to return results. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
