On Thu, Jan 28, 2010 at 9:19 AM, Zooko Wilcox-O'Hearn <[email protected]>wrote:
> Folks: > > [snip] > This has three beneficial effects: first, if there is a server on the > grid which is in a hung state such that it keeps its TCP connections > open but doesn't answer queries, then with current trunk all > downloads from that grid will stall indefinitely. With #928, that > hung server will have no deleterious effect on downloads at all > (provided that K shares can be found on other servers). Second, the > servers which answer the query fastest are the ones that the > downloader uses, which hopefully means that the servers that have a > faster connection to the downloader are the ones that get used, so: > faster downloads! This effect should be more pronounced on grids with > heterogeneous and geographically dispersed servers than on grids with > a bunch of homogeneous servers on the same LAN. Third, servers that > are busier will tend to answer the queries later, so this patch makes > downloaders automatically load-balance to download shares from > servers that are less busy. > Whoa! "Third, servers that are busier will tend to answer the queries later, so this patch makes downloaders automatically load-balance to download shares from servers that are less busy." There's a gem right there.... This could actually be built into the server to either 1) delay reply based on load, or 2) include some kind of load-indicating scaler (sanitized) to help the client better choose servers to download from. .... maybe. ...Complicated. Oh, well. jody
_______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
