[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 'svnadmin load' & database sync options

From: Oliver Jowett <oliver_at_opencloud.com>
Date: 2004-07-20 11:30:49 CEST

Replying to myself..

Oliver Jowett wrote:

>> oliver@cyclone:~/svn-test$ svnadmin create --bdb-txn-nosync repo-no-log
>> oliver@cyclone:~/svn-test$ echo "set_flags DB_TXN_NOT_DURABLE"
>> >>repo-no-log/db/DB_CONFIG oliver@cyclone:~/svn-test$ svnadmin recover
>> repo-no-log
>> Please wait; recovering the repository may take some time...
>> Recovery completed.
>> The latest repos revision is 0.

Don't do this, not even just for the initial load. It seems you can't
safely turn off DB_TXN_NOT_DURABLE once set; 'svnadmin recover' is not

I found a better solution in the end: put the new repository on a
memory-based filesystem (e.g. tmpfs). fsync() is then essentially free
so 'svnadmin load' is fast. Once it's done, copy the resulting
repository somewhere persistent.

Doing that reduced my load time from 2.5 hours to 15 minutes.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 20 11:31:14 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.