Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If it's an older SVN repository (or even quite new, but wasn't setup optimally), it maybe using the older BDB style of repository database. <a href="http://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs" rel="noreferrer">http://svn.apache.org/repos/asf/subversion/trunk/notes/fsfs</a> has notes on the new one. To change from one to another isn;t too hard - dump the entire history, re-initialise it with the new svn format of file system and re-import. It may also be useful at the same time to filter the repo-dump to remove entire checkins of useless information (I, for example, have removed 20MB+ tarball files that someone had checked in).</p> <p>As far as general speed goes - a quality (speedy) hard-drive and extra memory for OS-based caching would be hard to fault in terms of increasing the speed of how SVN will work.</p> <p>On the client side, if you have tortoisesvn setup through PuttyAgent for SSH access to an external repository machine, you can also enable SSH compression, which can also help.</p> <p><strong>Edit:</strong> SVN v1.5 also has the <a href="http://svnbook.red-bean.com/en/1.5/svn.reposadmin.maint.html#svn.reposadmin.maint.tk.fsfsreshard" rel="noreferrer">fsfs-reshard.py</a> tool which can help split a FSFS based svn repository into a number of directories - which can themselves be linked onto different drive spindles. If you have thousands of revisions, that can also help - if for no other reason than finding one file among thousands takes time (and you tell tell if thats a problem by looking at the IOwait times)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload