Perforce Server

P4D, the Perforce Server, is the engine that powers Perforce's shared versioning service and manages the Perforce shared 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.

Fast, Reliable Architecture

Responsible for managing the versioned files and stored metadata that records all user and file activity, P4D uses the native operating system to manage files; no customized file systems 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.

Proven Performance and Scalability

Perforce's lock on performance and scalability rests firmly on a lean design allowing you to support teams of thousands of users. 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.

Intelligent Branching with Perforce Streams

Perforce Streams provide a flexible workflow that simplifies branch and merge operations. Streams promote efficiencies such as code re-use, automated merging, fast context switching, efficient workspace updates, and inherited workspace and branch views. Perforce keeps track of all branches and merges, and ensures that changes are implemented in the right place and order.

Easy to Administer

P4D 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. P4D can log individual file access to a logfile if required for audit compliance. P4D features built-in replication and failover capabilities. One part-time administrator can typically manage a Perforce installation of hundreds of users.

Replication Technology

Perforce replication technology provides advanced capabilities to support large user bases, remote teams, and automated processes. Replica configurations include:

• A smart proxy replica provides fast, local read-only operations while relaying write activity to the shared versioning service.
• A build server replica supports all the usual activity for an automated process such as continuous integration, with no impact on the shared versioning service.
• A standard replica provides a complete read-only copy of the data kept in Perforce, making for a simple disaster recovery or backup solution.