From owner-freebsd-arch@FreeBSD.ORG Fri Apr 8 15:11:38 2005 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B111016A4CE for ; Fri, 8 Apr 2005 15:11:38 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C17743D1D for ; Fri, 8 Apr 2005 15:11:38 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id j38FBbrt032904 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 08:11:37 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.13.1/8.13.1/Submit) id j38FBa4B048590; Fri, 8 Apr 2005 08:11:36 -0700 (PDT) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4254E2E9.2090504@wadham.ox.ac.uk> Date: Fri, 08 Apr 2005 08:11:36 -0700 (PDT) From: John Polstra To: Colin Percival X-Bogosity: No, tests=bogofilter, spamicity=0.450984, version=0.14.5 cc: freebsd-arch@freebsd.org Subject: Re: Adding bsdiff to the base system X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2005 15:11:38 -0000 On 07-Apr-2005 Colin Percival wrote: > The reason portsnap is more efficient lies in how portsnap and CVSup > determine which files need to be updated. The ports tree contains > roughly 71000 files, and the first thing the CVSup client does is list > all of these files and send that list to the server. > > In contrast, portsnap has an index file -- containing, roughly speaking, > that same list -- and the portsnap client merely sends the sha256 hash of > this index file to the server, which responds with either "I recognize > that index -- here's a patch which will turn it into the latest index" > or "I don't recognize that -- here's the new index". Nice! John