问题描述
我们计划在网络自身是很慢的环境中安装Subversion库。
在previous VCS使用有VSS，这是一场噩梦使用它（不仅是因为它的功能）。
We plan to install a Subversion repository in an environment where the network is quite slow on its own.The previous VCS used there was VSS, and it was a nightmare to use it (not only because of its "feature").
所以，我的问题是Svnserve的和Apache模块之间的选择。我知道，Apache模块会慢一些，由于无状态协议，但我不知道有多少是它意味着时间的增加。
有没有什么地方一些基准和规则，指示速度的两个服务器之间的平均差异？
So, my question is the choice between Svnserve and the apache module. I know that the apache module will be slower due to the stateless protocol, but I've no idea how much is the increase of the time it implies.
Is there somewhere some benchmarks or rules that indicate the average difference of speed between the two servers?
推荐答案
资源，
在大多数情况下，如果版本控制系统，Subversion的性能进行了讨论，主题围绕所使用的存储库后端旋转（Berkeley数据库（BDB）与FSFS）和调整了一些服务器软件甚至硬件参数。
这似乎是少为人知的是使用的服务器变量的选择 - 在Apache Subversion的mod_dav_svn的模块或独立svnserve服务 - 必须测量和感知颠覆性能有很大的影响。
通常svnserve会比Apache的mod_dav_svn
It seems to be less known that the choice of the server variant used - the Apache Subversion mod_dav_svn module or the standalone svnserve server - have a great impact to measured and perceived subversion performance. Usually svnserve is significantly faster than Apache mod_dav_svn
在合成的，我使用Subversion 1.4.5，1.1.1颠覆和Apache 2.0进行非再presentative基准测试中，mod_dav_svn的业绩是30％到400％，比的svnserve的慢。 svnserve的性能接近使用svn命令行工具本地直接访问到存储库。
In a synthetic, non-representative benchmark test I performed using Subversion 1.4.5, Subversion 1.1.1 and Apache 2.0, mod_dav_svn's performance was 30% to 400% slower than svnserve's. svnserve's performance was close to local direct accesses to the repository using the svn command line tools.
最显著的性能损失是SVN的日志中测量和svn合并针对的mod_dav_svn服务器操作 - 你是否如立即注意到糟糕的svn日志性能。使用Eclipse插件颠覆Subclipse中。
The most significant performance penalty was measured during svn log and svn merge operations against the mod_dav_svn server - you'll notice worse svn log performance immediately if eg. using the Eclipse Subversion plugin Subclipse.
作者还提供比较两个。
我运行snvserv供应在后端约50库，并在没有任何投诉的性能。作为一个侧面说明目前只有10个用户，虽然。
I run snvserv that serves about 50 repositories on Berkely DB backends and have had no complaints on the performance. As a side note there are only 10 users, though.
我居然发现的svnserve非常易于安装和维护，不会惩罚你缺乏期货。 SSH可以为svnserve的和基于路径的安全性被激活也可以，如果你是一库，很多项目的那种人史蒂夫罗宾斯谈到：）
I actually found svnserve very easy to install and maintain and doesn't penalise you in lack of futures. SSH can be enabled for svnserve and path based security is also possible if you're the '"one repository, many projects" kind of guy' Steve Robbins talks about :)
这篇关于Svnserve的mod_dav_svn的VS的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！