That only works if you have the bandwidth to actually get the data to the validator. The problem at the moment in SETI is the last mile of internet connection. There are several possible solutions, but having the upload servers else where does not really help that much. The uploaded data still has to go through that last mile.
jm7 [email protected] wrote on 07/14/2009 10:51:19 AM: > Carl Christensen <[email protected]> > Sent by: [email protected] > > 07/14/2009 10:51 AM > > To > > [email protected] > > cc > > Subject > > Re: [boinc_dev] Optimizing uploads..... > > > there are plenty of good server-side means to handle failed uploads > without having to fiddle with the BOINC client; I think it comes > back to a project needing to do some homework and take some blame if > they vastly underestimated number of uploads, bandwidth etc. > > for example, on CPDN at our peak when we had huge uploads we were > able to setup a round-robin DNS system so that the same upload URL > could go to one of three physical servers. then we used > mod_backhand in apache for more intelligent load balancing, then > simply have a bunch of upload URL's in our workunits so if one fails > it just goes to another one (we had 10 upload servers federated > around the world at one point). these server-side mechanisms to > deal with things are much more flexible and sensible than trying to > cram a "one size fits all" solution in a BOINC client. > > > > _______________________________________________ > 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. > _______________________________________________ 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.
