From owner-freebsd-current Fri Jan 21 18: 0:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 51A4514F87; Fri, 21 Jan 2000 17:59:27 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA73880; Fri, 21 Jan 2000 20:56:59 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 21 Jan 2000 20:56:29 -0500 (EST) From: Chuck Robey To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <20000121173923.A44132@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, David O'Brien wrote: > On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote: > > I don't know ... I think it might be a good idea for the cvsup client to > > make a connection to a cvsup master, get redirected from that master to > > the actual handler of the connection, and then work. That way, a config > > file on the master could be set up to know the capabilities of the other > > machines (network availability, machine speed, etc) and dole out > > connections weighted on that. > > How is a cvsup master to know anything about the path from me to any > given cvsup mirror? Knowing something about the path from me to the > master and the path from the master to the mirror tells zero about the > path from me to the mirror. > > Being on an .EDU network, I have a *very* different path to other .EDU > machine participating in Inetnet2. My path to cvsup3 is a prime example. > This "cvsup master" will have no idea about this. I guess it means, is the main component trying to be balanced the server resources or the network resources. I may be wrong, but I think that the server resources are more likely to be the most important bottleneck, and this method detects that, with minimal network effects. If you think that it's really the network that's going to be the bottleneck, then you wouldn't want to use this method. I don't think I'm wrong, but I'm willing to listen to arguments on it. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message