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

Re: Need for a local Subversion server?

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 22 Jul 2011 19:58:04 +0200

On Fri, Jul 22, 2011 at 10:12:31AM -0700, Phil Montgomery wrote:
> I have a question regarding the need of a subversion mirror server.
> Our work is done on UNIX systems. We currently have a master repository in
> England. We mirror it as a read only repository to the states. The system
> that acts as the Subversion server in the states is rather old and its
> faster to do checkouts from the remote repository then the local one. I?m
> curious why we even need a local subversion server. We cannot add anything
> to the local repository. Developers check out the code, update the files in
> their working directory, then commit them to the remote server.
> Now trying to commit, resolve conflicts, and merges are another matter.
> Latency has a far greater impact on those tasks. We often thought about
> making a post-hook on the commit to initiate syncs from the master to the
> remote site in order to do the conflict resolution locally, allowing our
> developers to use a GUI interface or type in their xterm and not wait for
> the characters to appear. We have yet to do that test to see if it would
> help.

Have you considered using a write-through proxy setup?
See http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html
> (We did try the WanDisco Enterprise solution and like it, but in a spending
> freeze so absolutely no funds for that product)

The write-though proxy feature that ships with Subversion provides
similar advantages. The only major difference is that write operations
are proxied through to the master server, and must be copied back to
the slave server. So there is a time window where the slave isn't
up-to-date. It still provides major advantages for read-only operations,
and this speeds up lots of things, including merges. Basically, anything
but commit operations can be answered from the local server so there
is little latency.

The subversion project itself uses this type of setup with the
Apache Software Foundation's Subversion server, where our own
code is hosted. There is one server in the US (which acts as the
master server) and one in Europe (which acts as the slave).
svn.apache.org resolves to a different address depending on location.
Received on 2011-07-22 19:58:44 CEST

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.