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

Re: Estimation of repository upgrade

From: Giulio Troccoli <giulio.troccoli_at_mediatelgroup.co.uk>
Date: Fri, 05 Aug 2011 17:17:22 +0100

On 05/08/11 17:11, Nico Kadel-Garcia wrote:
> On Fri, Aug 5, 2011 at 10:58 AM, Bob Archer<Bob.Archer_at_amsi.com> wrote:
>
>> Has anything been done to improve the speed of a load. Last time I did it, when moving from 1.5 to 1.6 it took over 12 hours. And now, two years later the repo is probably quite a bit bigger (because we stupidly store binaries in it, I might change that when upgrading to 1.7).
> You can pre-configure by using svnsync to pre-create a new repository,
> and replicate relevant configuration files or scripts manually when
> ready to switchover. This is what I've used for migrating between
> servers that do not have shared back end storage, especially when
> updating operating systems and Subversion releases on the servers.

Thanks Nico, I was thinking along those lines. However, the need for an
upgrade is mostly for bug fixes and the fact that 1.4 is out of support.
We will not use any (that I know of) of the new feature in 1.6 so I'm
not even sure now if we need to run an svnadmin upgrade a all.
Received on 2011-08-05 18:17:55 CEST

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.