我们计划在网络本身速度很慢的环境中安装 Subversion 存储库。 之前使用的VCS是VSS，使用它简直就是一场噩梦(不仅仅是因为它的“功能”)。
所以，我的问题是 Svnserve 和 apache 模块之间的选择。我知道由于无状态协议(protocol)，apache模块会变慢，但我不知道它意味着时间增加了多少。
是否有一些基准或规则表明两台服务器之间的平均速度差异？
最佳答案
取自 this resource ,
In most cases, if the version control system Subversion's performance is discussed, the topics revolve around the repository backends used (Berkeley DB (bdb) vs. FSFS) and tuning some server software or even hardware parameters.
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
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.
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.
作者还提供了a benchmark两者比较。
我运行 snvserv，为 Berkely DB 上的大约 50 个存储库提供服务后端并且对性能没有任何提示。顺便说一句，不过只有 10 个用户。
我实际上发现 svnserve 非常容易安装和维护，并且不会因为缺乏 future 而惩罚你。可以为 svnserve 启用 SSH，如果您是 Steve Robbins 所说的“一个存储库，多个项目”类型的人，那么基于路径的安全性也是可能的:)
关于svnserve VS mod_dav_svn，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/502585/