> On Fri, Aug 5, 2011 at 10:11 AM, Giulio Troccoli
> <giulio.troccoli_at_mediatelgroup.co.uk> wrote:
>
>
> On 05/08/11 14:18, Mark Phippard wrote:
>
> On Fri, Aug 5, 2011 at 7:09 AM, Giulio Troccoli
> <giulio.troccoli_at_mediatelgroup.co.uk
> <mailto:giulio.troccoli_at_mediatelgroup.co.uk>> wrote:
>
> I'm working on a plan to upgrade our server from 1.4.6 to 1.6.17.
>
> We have 75 repositories, with an average size of 30MB. They're not
> big, I agree, but I wonder if anyone has any tip on how to
> estimate how long the "svnadmin upgrade" command will take. I
> mean, will it be a matter or minutes or hours?
>
>
> svnadmin upgrade runs in literally a few milliseconds. All it does is change the
> format number of the repository. If you want to fully move to all of the new
> repository features in 1.6 you have to do dump/load which will take longer.
>
> Wouldn't svnadmin upgrade give me the exact same thing as a dump/load
> cycle? If not, what would be different?
>
> svnadmin upgrade bumps the repository format number which allows certain
> new features to be used. But there are other things like representation-
> sharing that require a full dump/load to get.
>
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).
BOb
Received on 2011-08-05 16:59:10 CEST