From owner-freebsd-stable Wed Nov 22 1: 8:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id 398B437B4CF for ; Wed, 22 Nov 2000 01:08:50 -0800 (PST) Received: from rover (dialup-24-0-25-65.corp.home.net [24.0.25.65]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id BAA04424; Wed, 22 Nov 2000 01:08:41 -0800 (PST) From: "Sameer R. Manek" To: "Scott dodson" , Cc: Subject: RE: Solution for distributing CVS server load? Date: Wed, 22 Nov 2000 01:08:41 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200011210528.AAA33444@gsaix2.cc.GaSoU.EDU> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Future versions of the cvsup client may want to borrow the technology that's used in multi-player games, such as quake. A central server, such as cvsup.freebsd.org, has a listener on it, that provides the cvsup client with a list of public cvsup servers. The client then performs an application level "ping", similar to the oracle tnsping, where server load is also relayed to the client. The client can then pick server based on closet server + closest available server. Unfortunately my knowledge of how cvsup works is rather limited, so I have no idea if this is feasible to implement, or where to begin, to implement this. Sameer > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Scott dodson > Sent: Monday, November 20, 2000 9:36 PM > To: stable@freebsd.org > Subject: Solution for distributing CVS server load? > > > CVSUP updates configuration files as well. So why not have it update a > generalized map of some sort. Then cvsup will determine based on the > hostname/traceroute from the particular host to a known server (say > www.freebsd.org) where the host lies. Then determine if it's part of > a huge ISP such as UUNET and have one server designated for a group > of large ISPs based on number of hops to a certain cvsup server. > This should hopefully scale without much attendence since it will > be unlikely that suddenly everyone on UUNet (or other large ISP) > decides to use FreeBSD. > > I'm sure I'm overlooking something major, but this sounds like a possible > solution. > > -- > scott > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message