From owner-freebsd-current  Fri Jan 21 17:39:47 2000
Delivered-To: freebsd-current@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1BED5155C5; Fri, 21 Jan 2000 17:39:43 -0800 (PST)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA59492;
	Fri, 21 Jan 2000 17:39:40 -0800 (PST)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <200001220139.RAA59492@gndrsh.dnsmgr.net>
Subject: Re: Please help spread the CVSup mirror load more evenly
In-Reply-To: <200001220133.RAA23696@rah.star-gate.com> from Amancio Hasty at "Jan 21, 2000 05:33:21 pm"
To: hasty@rah.star-gate.com (Amancio Hasty)
Date: Fri, 21 Jan 2000 17:39:39 -0800 (PST)
Cc: obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra),
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > > Hi David,
> > > 
> > > John can implement a ping echo packet protocol for cvsup whose
> > > response can have "cool" information on the server. Steven's
> > > book on Networking already has the code for doing network latency
> > > calculations . It is more like if John has the time to implement
> > > such scheme ....
> > 
> > You don't even need to modify the protocol.  Just write a small
> > tcp program that times the 3 way handshake on open to all the
> > servers, take the one with the sortest time and spit that out
> > for the user to stuff in his cvsupfile.
> > 
> > 15 lines of perl should be more than enough :-)
> > 
> Hi,
> 
> Thats gross server load balancing . The network travel time
> does not tell you how how loaded the machine is or the server.

It may be gross to the server but it is optimal to the networks :-)

> 
> There are  couple of RFCs on network load balancing with 
> respect to servers or services and I am sure that there
> are also widely available research papers. 

Most of those concentrate on balancing the load on the server
itself.  How about balancing the load on the network paths,
I doubt very much that we have a server load problem near as
much as we have a network load problem due to people not
having ready access to the data that says ``this server is
closest network wise to me''.


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)               rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message