On Sat, Apr 18, 2009 at 09:51:38PM -0400, Bob Archer wrote:
> Hi All...
> I am upgrading from 1.5.5 to 1.6.1 today. Up to this point I have only
> 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 repo.
> Is this normal. I see in the book it talks about doing a nightly dump
> so you can back up. Do people really run dumps that take 4+ hours?
This rings a bell.
I have been told by a user of an svnadmin dump that took 9+ hours.
I have been meaning to reproduce the problem but did not have the time.
(No pun intended! :)
In that particular case it was reported that the dump took _longer_
when started incrementally from a revision somewhere in the middle of
revision history than when taking it from revision 0 on onwards.
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 can
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:
env CFLAGS="-pg" ./configure; make; make install
Then run svnadmin. It will create a file called "gmon.out" that you can
run through gprof to obtain statistics:
gprof /path/to/svnadmin gmon.out
Please send the generated statistics to the developer list.
They should not contain any sensitive data (but if they do, you can
also mail them to me privately if you wish).
I don't know what the equivalent on Windows is but maybe someone else can
comment on that if necessary.
If you can even provide profiles for full / incremental dumps for several
versions (e.g. 1.4, 1.5, and 1.6), we have a good chance to see when the
problem was introduced, if it has not been there all along -- which would
surprise me because people would probably have complained about it before.
But a profiled run of a full and incremental dump with 1.6 or trunk would
be the best place to start.
Received on 2009-04-19 14:57:24 CEST