David Anderson wrote: > If you have a build environment, check out the trunk and build. > Otherwise we'll have to wait for Rom to either backport this to 6.6 or 6.8. > > -- David > > Lynn W. Taylor wrote: [---] >>>> So, when any retry timer runs out, instead of retrying that WU, retry >>>> the one with the earliest deadline -- the one at the highest risk.
Beware the case where an upload fails because of some db or storage problem for a singular WU... One problem WU upload shouldn't cause all others to fail. I suggest use round-robin ordering when any upload fails (after all, no WUs are getting through in any case) and use earliest deadline first order only when any upload has succeeded. A second idea is to have the Boinc *client* dynamically reduce it's upload data rate in real time if it detects any lost data packets (detects TCP resends). The upload is abandoned for a backoff time if the upload rate reduces to too low a rate. This is a more sensitive attempt to avoid a DDOS on the project servers than just using an arbitrary backoff mechanism. Note that a saturated link has a much LOWER effective bandwidth than a maximally utilised link. Regards, Martin -- -------------------- Martin Lomas m_boincdev ml1 co uk.ddSPAM.dd -------------------- _______________________________________________ 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.
