Message-ID: <jwv3bz7rqxk.fsf-monnier+gmane.comp.version-control.arch.user@gnu.org>
To: gnu-arch-users@gnu.org
References: <pan.2004.11.18.13.23.45.365921@progsoc.org>
From: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Thu, 18 Nov 2004 12:48:58 -0500
In-Reply-To: <pan.2004.11.18.13.23.45.365921@progsoc.org> (Anand Kumria's
	message of "Fri, 19 Nov 2004 00:23:51 +1100")
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Gnu-arch-users] Re: cacherev policy script
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 913
Lines: 25
> In 'Archive Cached Revisons' from 
> <URL: http://regexps.srparish.net/www/arch-tech.html>, 
> it talks says an optimal cacherev policy would be "cached revisions such 
> that the sum of the sizes of changesets between any two cached revisions 
> is about the same as the size as the [...] cached revision."

> I'm just wondering if anyone has implemented a script to do this.

Assuming cachedrev are mostly used to speed up the "initial checkout", and
assuming that initial checkouts are done in 99% of the cases on the latest
revision, the optimal policy might be to have a single cacherev, placed near
the latest revision.
This assumes you have the backbuilder, of course.


        Stefan


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/