So, a host that tries on average every two hours, and has 50 work units to upload is going to try to connect 600 times per day.
... times 180,000 hosts (for SETI) and you've got 1250 connections per second. If the first failed upload "counts" against all 50 pending work units, then you drop that to 25 per second. I know that I'm making some assumptions that may not be 100% valid, that it might not be a 50:1 reduction, but the concept is sound. Same with downloads, you've got the assignments, but if you're having trouble downloading, hammering the servers isn't the solution. Josef W. Segur wrote: > You're correct that skipped opportunities to try uploads do not count as > "failed", they simply don't count at all. Typical hosts with continuous > connection try again every two hours on average because the actual backoffs > are randomized, so get 12 retries a day until the upload problem is > cleared. Hosts with only one hour a day connectivity will retry at the > beginning of that one hour and have a 25% chance of another retry in that > one hour. > > With failed uploads disabling downloads, it seems to me that hosts with > limited connect times due to IT department restrictions ought to be > given the best possible chance of getting new tasks when they are allowed > to connect. _______________________________________________ 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.
