Lynn W. Taylor wrote: > Some sort of daemon on the upload server would then send work back to > the main site as quickly as possible without saturating the link. > > ... but you're still limited to 80 or 90 megabytes. > > It doesn't solve the problem (too many simultaneous connections) it just > moves the problem from client <--> upload server to offsite upload > server <--> onsite upload server.
That was the point of my "data aggregator" or "communications multiplexor" suggestion: just acting as a file-for-file forwarder gains you nothing, but reducing the number of individual connections at a pinch-point in the link might help. Something could intercept the million-plus daily connections at the gigabit head-end, and replace them with a thousand or ten thousand connections on the 100 Mbit link. > (As an aside: I'm not sure why the SETI upload servers have to be > off-line during a backup, unless they're sharing a volume with some > other process that gets backed up -- a dependency forced by not having > enough local disk space on the upload server??) Usually they stay online - last week was an exception, but we're back to normal today. The inbound Cricket graph is already starting to ramp up. _______________________________________________ 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.
