带有塑料SCM的超大型存储库 [英] Very large repositories with Plastic SCM

问题描述

我们正在研究Plastic SCM作为Subversion的替代产品，以用于我们产品的版本控制.除了非常庞大的源代码库之外，我们还有大量的二进制资产(主要是艺术品资产，还包括一些文档，AVI等).只是在上面加上一个数字-svn校验我们的Trunk分支的HEAD版本需要一个多小时的时间，并且磁盘上的大小约为9 GB.

We are investigating Plastic SCM as possible alternative to Subversion for version control with our products. We have a very large number of binary assets (mainly art assets, but also includes some documentation, AVIs, etc.) in addition to a very large source code base. Just to put a number on it - a svn checkout of our HEAD revision of the trunk branch takes a little over an hour and has a size on disk of ~9 GB.

在这样的环境中，是否有人对Plastic SCM有任何经验，或者可以向我介绍有关Plastic SCM的性能和处理大型存储库的白皮书或案例研究?谷歌搜索并没有真正改变客观研究的方式，只是Codice自己发表的东西.我也意识到Perforce在这种环境下表现非常好-我以前使用过它-但是我们是一个规模很小的团队，预算也同样小，并且Codice免费为小型团队提供此系统(社区版").

Does anyone have any experience with Plastic SCM in such an environment, or can refer me to some whitepapers or case studies on the matter of Plastic SCM's performance and handling of large repositories? Googling hasn't really turned much in the way of objective research - just stuff published by Codice themselves. I also realize that Perforce does extremely well in this environment - I've used it before - but we're a pretty small team, with an equally small budget, and Codice offers this system free for small teams ("Community Edition").

我非常接近将其安装在测试服务器上并对其进行尝试...但是想先发布问题，以免浪费别人的时间(如果有人已经在这样的环境中对其进行了尝试).预先感谢您的宝贵时间.

I'm very close to just installing it on a test server and trying it out...but wanted post the question first, so as to not waste my time if someone else has already tried it out in such an environment. Thanks in advance for your time.

更新02-FEB-2011::如果有人有类似问题并正在查看此问题，我只是进行了一次更新...我在相当普通的Windows 2008 Server计算机(2.8GHz)上安装了Plastic Core 2 Duo，4 GB RAM，存储库存储在本地网络的SAN上)，运行用于塑料存储库的SQL Server 2008 R2.导入Subversion修订历史花费了一段时间-不到三天-大约28000个修订.但是， SMOKIN' 可以快速地从Plastic重新签出新分支-与Plastic相比，使用Plastic只需花费4分钟，而如上所述，在Subversion上花费一个小时以上.到目前为止，我们印象深刻！

UPDATE 02-FEB-2011: Just an update in case anyone else has a similar question and is viewing this...I got Plastic installed on a pretty modest Windows 2008 Server machine (2.8GHz Core 2 Duo, 4 GB RAM, repositories being stored on a SAN on the local network) running SQL Server 2008 R2 for the Plastic repositories. The import of subversion revision history took a while - just under three days - ~28000 revisions. However, it is SMOKIN' fast to do a fresh checkout of a new branch from Plastic - just shy of 4 minutes with Plastic compared to over an hour on Subversion as described above. We're very impressed so far!

推荐答案

我们正在将自己从Perforce迁移到Plastic，我们的存储库约为360Gb， 太大了实际上，即使使用巨大的文件，它也可以无缝地工作.

We are moving ourselves from Perforce to Plastic and our repository is about 360Gb, so quite large too. It actually worked seamlessly even using HUGE files.

由于我们从事视频游戏行业，因此必须使用大文件，并且 您知道所有其他DVCS(Hg，Git)在处理它们时都会遇到问题.

Since we're in the videogame industry, large files are a must, and as you know all the other DVCS (Hg, Git) have issues handling them.

这篇关于带有塑料SCM的超大型存储库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！