> On Sat, Apr 18, 2009 at 09:51:38PM -0400, Bob Archer wrote:
> > I am upgrading from 1.5.5 to 1.6.1 today. Up to this point I have
> > been using svnadmin update. But, I decided it was time to do a
> > dump/load as many have recommended.
> > But, dumping one of our repo took about 5 hours. This is a 20GB
> > Is this normal. I see in the book it talks about doing a nightly
> > so you can back up. Do people really run dumps that take 4+
> I believe there may be problem, but we need some more data.
> What would really help is a run of svnadmin dump in a profiler so we
> see where it spends so much time. If you compile your own builds
> you can do that fairly easily. On *nix, just add -pg to CFLAGS:
> I don't know what the equivalent on Windows is but maybe someone else
> comment on that if necessary.
Yes, I am running on a Windows 2003 server. I just use the collabnet
binaries. What would be the procedure there?
> If you can even provide profiles for full / incremental dumps for
> versions (e.g. 1.4, 1.5, and 1.6), we have a good chance to see when
> problem was introduced, if it has not been there all along -- which
> surprise me because people would probably have complained about it
> But a profiled run of a full and incremental dump with 1.6 or trunk
> be the best place to start.
What I did was dump with 1.5.5 since that was the version I had
installed. Should I be upgrading first and dumping the old repo with the
most recent version? I was sure about that.
BTW: The load is still running. Been about 13hours at this point... It
looks like it is on about rev 28k or so.
Thanks for your help. If I knew it would take this long I would have
just done and svnadmin upgrade and lived with the extra 10% of disk
space that wouldn't save me.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-19 17:24:17 CEST