Perforation Warehouses

Question

Is it preferable to have one depot with several folders that map to different paths in the workspace. OR multiple folders in the same repository that map to multiple workspaces or multiple repositories for multiple workspaces.

Does anyone have practical advice on this?

I also noticed that when I have several folders in a depot that map to different paths in my workspace, when I differ from a depot, a change in one of the subfolders does not appear in diff.

Answer 1

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

The most significant difference from the configuration of several depots is that on the Perforce Server P4ROOT directory, each project is stored in its own catalog of top-level warehouses (and not as a subdirectory of one depot). Several configuration stores allow you to use the Map depot to place each top-level depot directory on, if necessary, a separate file system. More on using the Map field can be found in the Command Reference entry for p4 depot.

Efficiency is another consideration when setting up a single or multiple depot. Separation of projects into separate depots, file paths for many Persistent operations are inherently limited to a narrower range of files that scan specific database tables. the difference in performance depends on the specific data sets and their use. For many small installations, there are no noticeable differences. However, for larger installations and for some environments of use, the performance difference can be significant.