On 7/20/07, Brian Krusic <brian@krusic.com> wrote:
> Hello once again;
>
> When you guys at Tigris do your back end SVN updates from say repo version
> 1.3 to 1.4, etc....
>
> ... how do you go about it in terms of minimizing down time?
>
> I'm asking as we have about 5 repos each at about 40-60GB and based on our
> tests, the process of converting takes about 1.5 days per repo on a P3. We
> have serveral Opterons and Core Duos which we can spread the conversion
> process on that would speed this up.
>
> We figure 1 week total for implementation/debug. We are testing now but
> will most liely wait till 1,5 is out as the sync/proxy feature is shweeeet!
>
> I know that I am asking systems methodology advice, but since you guys do it
> all day long, it doesn't hurt to ask.
Did you know that you do not need to do this? You could have created
repositories with SVN 1.0 and still serve them with 1.4 as well as the
upcoming 1.5. I think there have been two releases where there were
some minor improvements you could get by doing a dump/load, but you
have never had to. The next release will add small a SQLite database
to the repository, as an example, and it will just get created the
first time it is needed.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 21 02:45:03 2007