From owner-freebsd-hubs@FreeBSD.ORG Thu Feb 6 02:32:45 2014 Return-Path: Delivered-To: hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D9A632D for ; Thu, 6 Feb 2014 02:32:45 +0000 (UTC) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801::36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5C25D1600 for ; Thu, 6 Feb 2014 02:32:38 +0000 (UTC) Received: from rwpc15.gfn.riverwillow.net.au (rwpc15.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:20c:76ff:fe0a:2117]) (authenticated bits=56) by mail1.riverwillow.net.au (8.14.8/8.14.8) with ESMTP id s162WKVF032092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Feb 2014 13:32:25 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=m1001; t=1391653945; bh=UL3mSE63TN9VHlmRrl550pc0BLobCXxwbXMviPjFpd4=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Z0aRT0IHcDkPYwT8AVAwS0/dwNMG1LhiugUYkrBKko/lmKBowEKPVDpsgupXvUf9z aHxpZViVjT4KuiD2Kbo/ksbH2OeFJeL3xPcPhvMKW0kbVjwk1qZXikWKY1Kams++OT tUXexHT8XlSEW2rf2oH0BOCvqX4dl8Z/hm8BXVVU= Date: Thu, 6 Feb 2014 13:32:20 +1100 From: John Marshall To: Peter Wemm Subject: Re: [hubs] cvsup-master changes Message-ID: <20140206023220.GC17736@rwpc15.gfn.riverwillow.net.au> References: <52F288CE.9070805@wemm.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p4qYPpj5QlsIQJ0K" Content-Disposition: inline In-Reply-To: <52F288CE.9070805@wemm.org> OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.22 (2013-10-16) Cc: hubs@freebsd.org X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 02:32:45 -0000 --p4qYPpj5QlsIQJ0K Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 05 Feb 2014, 10:54 -0800, Peter Wemm wrote: > In order to tidy up some no-longer-needed complexity with cvsup-master I'= ve > done a final rebuild of the infrastructure supporting it. It's now a self > contained slave of other public data. Thank you for all of your work on this, and thank you for letting us know. I _love_ the CNAME target! > - The source for the www mirror data is now the same rsync pool that is > used on www.freebsd.org. The old cvsup data was being gathered from an > obsolete machine that was only doing a partial build - large chunks were = 1+ > years stale. So now the www mirrors served from www/current replicas are more like real mirrors. Lovely! > - I purged the 1-2 year stale ports and doc trees. I'll upload tarballs = of > the final versions of each onto ftp shortly. I hope you don't get too much backlash from this. All CVSup mirrors and probably all CVSup ports tree users would have "default delete" in their supfiles. So, by deleting the ports tree on cvsup-master, you have replicated the tree deletion out to the world: their (very stale) ports trees would have been replaced with your README.ports file. It looks like this was your intention but it might come as a bit of a shock to some. Did you consider the option of removing the ports-all collection directory? Would you consider doing that anyway? That way the sup client will see, 'Server message: Unknown collection "ports-all"' without having its very own copy of the stale CVS ports tree deleted. In any case, I suggest that some folks might find it helpful to find an announcement on ports-announce@ and/or ports@ to the effect that the ports collection has been removed from the CVSup servers. > After looking at the machine's logs, I'm wondering how much this stuff is > being used by end users relative to the number of mirrors still in > operation. I suspect it is really difficult to tell the difference betwe= en > somebody who's actually using the code from cvsup vs somebody who set up a > mirror years ago and forgot about it. Given that 25% of our server's daily synchronization requests are for the ports-all collection, I would suggest that many of the sync's. fall into the "set and forgot" category. > There's a public cvsup machine in the cluster (cvsup14.nyi) that appears = to > be desperately bored lately. It implements 12 of the cvsupN aliases and > seems to be doing about 50 client connections per hour. Is this comparab= le > with what other folks are seeing? We saw a 60% reduction in CVSup traffic early last year when svn exports to the CVS ports tree ceased. With the current, release and stable src branches, ports, doc and gnats no longer being updated via CVSup, I would guess that the majority of what's left is "set and forgot", apart =66rom some actual users of the mail-archive/current and www/current collections - and some of those may be "set and forgot" too. The bulk of our remaining CVSup traffic is attributable to about half a dozen downstream private mirrors (some of which are telco, ISP and government - I have no knowledge of the degree of usage made downstream of any of those). Here are some real numbers from the past 9 months. The graphs start a couple of months after the 60% drop-off. The 10GB/day spikes are now ancient history. This server takes all traffic for cvsup.au and cvsup[2-7].au and is the only FreeBSD CVSup mirror in the South Pacific/Australasian region. http://cvsup3.au.freebsd.org/stats.html As far as I know, there is still no official svn mirror available this side of the Pacific, so most of our former CVSup clients have probably switched to svn and using svn0.us-west (~200ms away). --=20 John Marshall --p4qYPpj5QlsIQJ0K Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlLy9DQACgkQw/tAaKKahKJ8pgCgjqRqAX01Tp9b+/fDagQ2nVn9 4kwAnRj2hwM1pciCe1AkOUnI7EJ9EYTF =tQSH -----END PGP SIGNATURE----- --p4qYPpj5QlsIQJ0K--