Geek Answers Handbook

Is there faster centralized version control than SVN?

I have been using SVN for a long time, and now we are trying to use Git. I am not talking about centralized decentralized debate. My only concern is speed.

The last tool is much faster. But sometimes I NEED to work with a centralized approach, which is much simpler and less complicated than decentralized. The learning curve is very fast, which saves a lot of time (while tearing into a decentralized one will be a waste of time, given that the learning curve is much longer, and we face a bigger problem when working with it).

However, SVN is very slow compared to GIT, and I don't think it has anything to do with the centralized argument. Decentralized systems must also deal with server connections and file transfers. Therefore, I can easily assume that a quick implementation of centralized version control could exist.

Does anyone know about this?

+7
performance git version-control svn
source share
4 answers

One CVCS (Centralized Version Control System), which I know, much faster than SVN, is not free:

Perforce

I will talk about this in detail in the SO answer .

Perforce diagram

This document shows a comparison between Perforce and Subversion .
His support for the merger, in particular, is much more effective.

+5
source share

Git supports many topologies, including a centralized CVS / SVN approach. There are several options:

  • Provide a central shared repository via ssh. gitosis makes this easier.
  • Use github personal accounts.
  • Use the github commercial server product, github: fi, in your own data center.
+1
source share

What makes SVN slow in the way it handles working copies. Thousands of files are touched and recorded.

You can try Bazaar (bzr) as it supports workflows (but I don’t know if this really happens faster) or wait for SVN 1.7 with WC-NG and centralized metadata. SVN 1.7 is scheduled for this summer, but may also be completed later.

+1
source share

Git is very flexible and works great in a centralized layout. On a server somewhere, create a bare repository with something like:

mkdir repo cd repo git init --bare --shared

Then push your repository naked on the server and call it the “central” repo.

0
source share

More articles:


All Articles