Niel De Clerk wrote:
> Our repository is on one machine and svnserve runs (as a windows
> service) on another machine (same network) using a mapped network drive
> to the repository. Svnserve must run on the second machine because it
> has a fixed IP and is accessible through the firewalls to our various
> clients. The repository was installed on the other machine mainly
> because of backup etc reasons, but in theory it could be moved to the
> machine running svnserve (would this introduce a significant performance
> gain?).
This is a non-optimal configuration and I am highly confident you would see a
performance increase from moving the repository to the same server as the
service itself. While your configuration will "work" (for some value of work),
it is not efficient and there is even the possibility of corruption (this is
true of any networked filesystem access like this).
You have two choices:
1) move the repository to be local to the svnserve process;
2) switch to using http[s] access, and run a proxy service on the externally
accessible host and the Apache service on the box with the repo.
The second choice would keep your backup strategy intact, but would require all
WC to be updated with the new path (you can use `svn switch --relocate`, since
it is still the same repo). You also need to make sure that whatever proxy you
install on the outwards facing box doesn't mess with the traffic (which
some/many do). See this link for more details:
http://subversion.tigris.org/faq.html#proxy
HTH
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-07 13:26:33 CET