Subversion 与 SourceSafe 中的性能 [英] Performance in Subversion vs. SourceSafe

查看:21
本文介绍了Subversion 与 SourceSafe 中的性能的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们是一个由 5 名开发人员组成的分布式团队,致力于相当大的集成项目.我们目前使用 SourceSafe(是的,我知道它很糟糕,但它直到最近才起作用,我们一直在使用它).我们最近最大的问题变成了性能.签入和签出项目需要很长时间,而且我们发现自己花了很多时间来等待 SourceSafe(是的,我们已经关闭了防病毒检查和所有其他性能提升 Trix - 它仍然很慢).

We're a distributed team of 5 developers working on rather large integrations project. We currently use SourceSafe (yes I know it sucks but it has just worked until recently and we've used it forever). Our biggest problem has recently become performance. Checking in and out project just takes forever and we're finding ourselves spending a lot of time just waiting for SourceSafe (yes we've turned off anti-virus check and all the other performance boost trix - it's still slow).

我们现在正在考虑设置并将我们的所有内容转移到 Subversion.与 Subversion 相比,SourceSafe 在 web 上的性能如何? 我想移动历史并不是那么重要(如果我们需要旧文件,我们可以回到 VSS 数据库)和将文件实际移动到 Subversion 应该是个问题 - 对吗?

We're now looking into setting up and moving all our stuff to Subversion instead. How is performance in SourceSafe over the web compared to Subversion? I guess that the history isn't that important to move (we could just go back to the VSS database if we need an old file) and the the actually moving of files to Subversion should be a problem - right?

除了实际的 Subversion 核心工具之外,我还想对必须拥有"的工具和附加组件提出一些意见.

I'd also like to have some input on tools and add-ons that are "must have" besides the actual Subversion core tools.

推荐答案

VSS的签入在SVN中称为提交.此操作要快很多倍,因为 SVN 只会传输您对文件所做的更改(也称为差异"),而 VSS 将发送整个文件并在服务器上对其进行区分.

The check in of VSS is called commit in SVN. This operation is many times faster, as SVN will only transfer the changes (aka the "diff")you made to the files, while VSS will send the whole file and difference it on the server.

签出 与其他系统相比,SVN(获取初始工作副本)中的签出有点慢,如果您使用的是 http(s) 并且文件的总体大小很大 (>100MB).SVN 最坏的情况是大量文件和目录,因为 HTTP 传输将比大的单个文件慢得多.

the check out in SVN (getting an initial workingcopy) is somewhat slow in comparsion to other systems, if you are using http(s) and have a large (>100MB) overall size of files. SVN worst case is lot of files and directories, as HTTP-transfer will be much slower than big, single files.

然而,我怀疑 VSS 会比 SVN 更快.SVN 的整体性能比 VSS 更快、更健壮(没有数据库损坏)并且更容易理解.

However, I doubt that VSS will be faster than SVN. Overall performance of SVN is faster, more robust(no database corruptions) and easier to understand than VSS.

好的工具是 TortoiseSVN(Explorer Plugin)、smartSVn(VSS-lookalike) 和 commandline(flexible)正如 Tigraine 在我的评论中添加的那样:AnkhSVN(Visual Studio 集成)和 subversive/subclipse for eclipse IDE

Nice Tools are TortoiseSVN(Explorer Plugin), smartSVn(VSS-lookalike) and commandline(flexible) as Tigraine added in my comments:AnkhSVN(Visual Studio Integration) and subversive/subclipse for eclipse IDE

这篇关于Subversion 与 SourceSafe 中的性能的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆