Jazz RTC 的文件后备存储？基于数据库还是基于文件？
目前，我们在大量大型项目中使用 Clearcase。我们在后台使用 SQL Server 作为文件存储，它最终达到了访问文件速度太慢的地步。
看看 GIT 和 Mercurial，我们看到了基于存储文件差异的分布式 VCS——它有可能获得更好的本地性能。
有谁知道 Jazz RTC 是否有由文件差异或数据库支持的文件存储？ （谣言表明它是由 DB2 支持的：/）
We currently use Clearcase for a large number of large projects. We use SQL Server as the file store in the background, and it has eventually reached a point where accessing files is just too slow.
Looking at GIT and Mercurial, we see a distributed VCS based on storing file differences - which has the potential to get much better local performance.
Does anybody know whether Jazz RTC has a file store backed by file differences or by a database? (The rumour mill is suggesting it is backed by DB2 :/ )
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我建议使用 Git 进行 VCS 和其他系统的问题跟踪、构建服务器等。一体化解决方案仅此而已。最初可能更容易开始，但你很快就会遇到“链条中最薄弱的环节”。
希望这有帮助
I would recommend on using Git for VCS and other systems for issue tracking, build servers, etc. The all-in-one solutions only go so far. Initially it may be easier to start, but you quickly run into the "weakest link in the chain".
Hope this helps
我想您指的是 Jazz RTC，它包含版本控制。
其 Jazz RTC 服务器 支持 DB2、Sql Server 和 Oracle。
但是，Jazz 平台与 Git 和 Mercurial 等 DVCS 非常不同：它是一个 应用程序中心旨在促进多个软件之间关于开发生命周期（需求、版本控制、更改、构建等）的通信。
版本控制部分只是Jazz的一小部分。
I suppose you mean Jazz RTC, which has a version control included.
Its Jazz RTC server supports DB2, Sql Server and Oracle.
However, a Jazz platform is very different from a DVCS like Git and Mercurial: it is an application Hub made to facilitate the communication between several software about the development lifecycle (requirements, versionning, changes, builds, ...).
The version control part is only a small portion of Jazz.
通过 RTC/Jazz 源代码控制进行文件访问速度很快。
在 Jazz SCM 开发团队（我是其中的一员）中，我们有一个大型存储库。它包含数万个文件和数十万个文件状态。加载时间（在我们的 LAN 上）受到网络速度的限制：我可以在 10 到 20 分钟内加载 50k 文件（大约 500megs）。在更快的网络上，效果会更好。
在服务器上，更改在适当的情况下保留为增量（即版本之间的差异）。 Jazz 服务器由数据库支持，但访问速度很快。
File access with RTC/Jazz source control is fast.
On the Jazz SCM dev team (of which I'm a part), we have a large repo. It contains tens of thousands of files, and hundreds of thousands of file states. The load time (on our LAN) is limited by network speed: I can load 50k files (roughly 500megs) in 10 to 20 minutes. On a faster network, it would be better.
On the server, changes are kept as deltas (ie, differences between versions) where appropriate. The Jazz server is backed by a database, but access is quick.