P4D, the Perforce Server, manages the Perforce central file repository, or depot. P4D handles user requests and tracks development activity in the built-in Perforce database. No special hardware is needed, other than storage for depot and database files.

Details

Architecture

The Perforce Server is responsible for managing the versioned files and the stored metadata that records all user and file activity. P4D uses the native operating system to manage files; no customized filesystems are necessary. Client files are stored on the user's machine; no network access is needed for ordinary user activity such as editing or compiling.

Performance and scalability

Perforce's lock on performance and scalability rests firmly on three pillars of design. A carefully keyed relational database ensures rapid response times. An efficient streaming network protocol minimizes the effects of latency. An intelligent, server-centric data model is network friendly and keeps the database performing at top speed.

Cross-platform availability

Perforce is available on a wide variety of platforms, including Windows NT/2000/XP/2003 and most Unix/Linux operating systems. For an up-to-date list of the specific platforms on which P4D runs, see the Perforce Downloads page.

Managing third-party code drops

If your company regularly imports or exports code from other organizations, Perforce provides a remote code drop facility to simplify the procedure. A remote depot can refer to another server in a different location; the files required for the code drop can be transferred with a single command.

Ease of administration

The Perforce Server is easy to install and administer. No third-party databases or application servers are required. User authentication is supported for external data sources such as LDAP and Active Directory. The server can log individual file access to a logfile if required for audit compliance. One part-time administrator can typically manage a Perforce installation of hundreds of users.