Helix Core Server Administrator Guide: Multi-Site Deployment (2018.2)

Introduction to federated services

Helix Core Server Administrator Guide: Fundamentals explains how you create, configure, and maintain a single Helix Core Server. Small organizations often find a single server is adequate to meet user needs. However, as the business grows and usage expands in scale and geography, many organizations deploy a more powerful server-side infrastructure.

Architecture	Advantage	Disadvantage
Helix Proxy	easy to install, configure, and maintain improves performance by caching frequently transmitted file revisions reduces demand on the Perforce service and the network over which it runs no need to back up the proxy cache especially beneficial with larger files	not optimal for syncing large numbers of small files Tip A proxy cannot be deployed in front of a forwarding replica See the Support Knowledgbase article on Proxy Performance.
Helix Broker	rule-based load distribution that typically frees the master from "read commands" well-suited for builds from the read-only replica facilitates swapping the servers for a checkpoint or upgrade Tip Can display a friendly "Down for Maintenance" message when the p4d process is offline for maintenance or failover (as opposed to a TCP connect error)	broker layer causes some overhead in network performance see the Support Knowledgebase article, "Using P4Broker to redirect read-only commands".
Forwarding replica	customizable filtering supports "daisy chaining" to additional sites. For example, a site in the Philippines might forward to a site in Taiwan that forwards to a site in Japan that forwards to the Master in France. This alternative to directly connecting each Asian site to Europe: reduces the metadata replication load on the master server reduces the amount of data traveling across the WAN from Europe to Asia For more information, see the Knowledge Base article on server-to-server arrangements, "Helix replication rules".	"write" commands are slower because local metadata must be pulled from the master requires machine provisioning and administration. See Configuring a forwarding replica. Tip Starting with 2018.2, we recommend a standby server with rpl.journalcopy.location=1 for high availability and disaster recovery.
Commit-edge	best performance overall because most commands are local	cannot be used as a warm standby requires machine provisioning and administration, including backups of each edge

Tip

For a more detailed summary of replica server types, see the Support Knowledgebase article, "Replica Types and Use Cases".

Other types of federated architecture

A federated architecture might also include servers dedicated to centralized authorization and changelist numbering. See Configuring centralized authorization and changelist servers.

Your search for returned result(s).