On 28.09.2011 07:18, Daniel Shahaf wrote:
Wouldn't it also be useful to pass --deltas to 'svnadmin dump'?
Of course, you are absolutely right!
-- Stefan^2.
I should note the advice below only applies to FSFS-backed repositories.
Stefan Fuhrmann wrote on Tue, Sep 27, 2011 at 11:11:45 +0200:
Stümpfig,
Thomas<thomas.stuempfig_at_siemens.com<mailto:thomas.stuempfig_at_siemens.com?Subject=Re:%20svn%20upgrade%20with%20dump/load>>
wrote:
I plan to upgrade a 250GB Repository from 1.5 to 1.7. As I learned
>from other threads in this list, it is wise to dump and load the
repository in order to bring everything to the latest features.
I have to keep the revision numbers and transaction dates.
Now svn dump and load offer some flexibility. And my server has
32GB Memory and 16 Cores.
Now, in order to optimize the migration process would it be worth
to split the dump into multiple dumps? And if yes, would you use
delta dumps?
Hi Thomas,
You can use the 1.7 binaries for both, dump and load.
Version 1.7 svnadmin has a new "-M" parameter that
allows for using large caches for this kind of operations.
On your machine, you could set 16G aside for the
migration and do something along the lines of:
svnadmin dump -M 8000 $old | svnadmin load -M 8000 $new
The performance limiting part is the replaying of all
commits on the load side. If possible, make the /db/transactions
and /db/txn-protorevs of the target point to some RAM disk.
-- Stefan^2.
