Perforce 仓库

发布于 2024-08-28 07:01:15 字数 174 浏览 4 评论 0原文

是否最好让一个软件仓库包含多个文件夹,这些文件夹映射到工作区中的不同路径。或者一个仓库中的多个文件夹映射到多个工作区,或者多个仓库映射到多个工作区。

有人对此事有任何实际建议吗?

我还注意到,当我在仓库中有多个文件夹映射到工作区中的不同路径时,当我与仓库进行差异时,子文件夹之一的更改不会显示在差异中。

Is it preferred to have one depot with multiple folders which map to different paths in a workspace. OR multiple folders in one depot that map to multiple workspaces, or multiple depots to multiple workspaces.

Does anyone have any practical advice on the matter?

I've also noticed that when I have multiple folders in a depot that map to different paths in my workspace when i diff from the depot a change in one of the sub folders does not show up in the diff.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

梦里南柯 2024-09-04 07:01:15

根据您仓库的大小,我认为这更多是一个品味问题。我们目前有两个不同的仓库,但主要是因为它们本质上是分离的(//sw//data/)。 Perforce 知识库 说:

最显着的区别是
多仓库配置是
在 Perforce Server P4ROOT 中
目录,每个项目都存储在
它自己的顶级仓库目录
(而不是作为
单一仓库)。多车场
配置允许您使用
仓库“地图”字段放置每个
顶级软件仓库目录
如果需要的话,单独的文件系统。更多的
有关使用地图字段的信息,请参见
p4 的命令参考条目
仓库命令。

性能是另一个考虑因素
配置单个与多个
仓库。通过将项目拆分为
独立的仓库,许多文件路径
Perforce 操作本质上是
限制在更窄的范围内
文件,从而减少需要
扫描某些数据库表。这
性能差异取决于
特定的数据集和用途。
对于许多小型安装,有
没有明显差异。然而,
对于较大的安装和一些
使用环境、性能
差异可能很大。

Depending on the size of your depots I think it is more a question of taste. We have currently two different depots, but mainly because they are disjunctive in their nature (//sw vs. //data/). The Perforce Knowledge Base says:

The most significant difference with
the multiple depot configuration is
that, in the Perforce Server P4ROOT
directory, each project is stored in
its own top-level depot directory
(rather than as a subdirectory of a
single depot). The multiple depot
configuration allows you to use the
depot "Map" field to put each
top-level depot directory on a
separate filesystem, if desired. More
on using the Map field can be found in
the Command Reference entry for the p4
depot command.

Performance is another consideration
in configuring single vs. multiple
depots. By splitting projects into
separate depots, file paths for many
Perforce operations are inherently
limited to a more narrow range of
files, resulting in reduced need to
scan certain database tables. The
performance difference is dependent on
the particular data sets and usage.
For many small installations, there is
no appreciable difference. However,
for larger installations and for some
usage environments, the performance
difference might be significant.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文