From owner-freebsd-current Mon Jan 24 10:55:51 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 3908F14C4C for ; Mon, 24 Jan 2000 10:55:44 -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 NAA78292; Mon, 24 Jan 2000 13:55:16 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 13:55:16 -0500 (EST) From: Chuck Robey To: Warner Losh Cc: Brad Knowles , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001241820.LAA04735@harmony.village.org> 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 Mon, 24 Jan 2000, Warner Losh wrote: > Agreed. The making lots of connections was a bad idea. However, I've > rarely seen low latency and low bandwidth go together. I've also > problems connecting accross high loss links more often. Sure, it is a > statistical argument. > > I still think that the n connections wouldn't be that expensive. The > cost, iirc, of a connection that drops is very low. I can certainly > see enough problems with it to encourage jdp to not implement it, > despite being the person that proposed it... That's the precise reason I suggested a system that used no probing, had feedback, and forced shared load in spite of user misconfiguration. Got shouted down. ---------------------------------------------------------------------------- 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