On Monday, the Subversion project is scheduled to release version 1.0 of their version control system, under development for several years now. Subversion was intended from its inception as the CVS replacement and it comes with many important features previously found only on commercial VCS like Perforce. It was designed for better remote performance, and it is multi-platform with a GUI/CLI front-end.
Permalink for comment
To read all comments associated with this story, please click here.
I did some speed tests a few weeks ago comparing Subversion and Microsoft Visual SourceSafe over a VPN. Adding a set of files and subdirectories to the repository took 1 minute 30 seconds (averaged over three runs) in Subversion, while VSS took 49:07 (only one run because it took so long).
Getting those same set of files took 0:30 in Subversion, but 7:25 in VSS.
I read somewhere that there are ways to speed up VSS so it works better over slow connections (aside from using something like SourceOffSite), but these tests were performed on a base system without any optimizations.
I did some speed tests a few weeks ago comparing Subversion and Microsoft Visual SourceSafe over a VPN. Adding a set of files and subdirectories to the repository took 1 minute 30 seconds (averaged over three runs) in Subversion, while VSS took 49:07 (only one run because it took so long).
Getting those same set of files took 0:30 in Subversion, but 7:25 in VSS.
I read somewhere that there are ways to speed up VSS so it works better over slow connections (aside from using something like SourceOffSite), but these tests were performed on a base system without any optimizations.