I'm currently reviewing the benefits of moving from SVN to a SourceGear Vault. Has anyone got advice or a link to a detailed comparison between the two? Bear in mind I would have to move my current Source Control system across which works strongly in SVN's favor

Here is some info I have found out thus far from my own investigations.

I have been taking some time tests between the two and vault seems to perform most operations much faster. Time tests used the same server as the repository, the same workstation client, and the same project.

Time Comparisons

• SVN

Add/Commit    12:30 Get Latest Revision    5:35 Tagging/Labelling    0:01 Branching    N/A - I don't think true branching exists in SVN

• Vault

Add/Commit    4:45 Get Latest Revision    0:51 Tagging/Labelling    0:30 Branching    3:23

(can't get this to format correctly)

I also found an online source comparing some other points. This is the kind of information i'm looking for.

Usage Comparisons

• Subversion is edit/merge/commit only. Vault allows you to do either edit/merge/commit or checkout/edit/checkin.

• Vault looks and acts just like VSS, which makes the learning curve effectively zero for VSS users.

• Vault has a VS plugin, but it only works if you're going to run in checkout-mode.

• Subversion has clients for pretty much every OS you can imagine; Vault has a GUI client for Windows and a command line client for Mono.

• Both will support remote work, since both use HTTP as their transport (Subversion uses extended DAV, Vault uses SOAP).

• Subversion installation, especially w/ Apache, is more complex.

• Subversion has a lot of third party support. Vault has just a few things.

My question

Has anyone got advice or a link to a detailed comparison between the two?