[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Will upgrade from 1.6 to 1.7 benifit from dump/reload?

From: Neels J Hofmeyr <neels_at_elego.de>
Date: Mon, 22 Feb 2010 13:35:52 +0100

(This mail was posted to dev@ -- redirecting to users@)

Johan Corveleyn wrote:
> Hi devs,
> A small question in anticipation of 1.7: will an (FSFS) repo benifit
> from a dump/reload when upgrading from 1.6 to 1.7? Or will a simple
> "upgrade" (followed maybe by a "pack" to pack the revprops) provide
> just the same?
> Reason for asking: We're currently still running on 1.5, and planning
> to upgrade to 1.6 soon. Tests have shown us that doing a dump/reload
> during this upgrade will give some benefit (due to rep-sharing
> probably), but nothing huge. So I'm just wondering whether to do a
> dump/reload now (to be in the best possible shape for the future), or
> that I'll have to do another dump/reload when going to 1.7 in order to
> get maximum benifits. In the latter case, I will probably not do a
> dump/reload now (just upgrade to 1.6), and defer that until we upgrade
> to 1.7...
> Kind regards,
> Johan

Just a side note, we are expecting most users to still be using 1.6 servers
with their 1.7 clients for a while. But 1.7 will probably move to SHA1
checksums instead of MD5, and there will be some duplicate checksum
calculation when pairing up a 1.7 client with older servers. ...but a)
duplicate checksums might also be necessary even with 1.7 client <-> 1.7
server, and b) we don't expect *that* to impact performance, really.

1.7 servers may also allow you to obliterate revisions, but we don't know
that yet.

Anyone else know of a particular server side improvement planned for 1.7?
(I'm rather ignorant, really)


Received on 2010-02-22 13:36:30 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.