This document outlines Perforce's roadmap to improve its distributed development capabilities, called "100X". Current solutions like filtered replication and task streams will be enhanced. The "100X" initiative aims to optimize failover, reduce network load, allow horizontal scaling, and improve concurrency. It includes advanced replication techniques like proxy replicas, filtered/chained commits, and Git replication. The roadmap's goals for 2014 are horizontal scaling of read operations, high availability and failover, and improved replication throughput. These changes will make remote sites faster and allow better support of large, distributed teams.

1. 1
Distributed Development Roadmap
Ralf Gronkowski
Product Specialist

2. 2
Perforce Today
Current Solutions

3. 3
13.1 Update
§ Filtered Replication
§ Task Streams
§ Unshelve to Branch
§ Submit Shelf

4. The Problem is…
4
§ Remote sites
§ Large teams
§ Automation
§ Git mirrors
Supporting

5. Versioning
Service
Proxy
Proxy
Replication
Service

6. 6
Road Map
New Solutions

7. 7
“100X” Initiative
“100X”
Data Center
Distributed
Today

8. 8
100X Includes…
FailoverDistributed
optimization
Reduced
network load
Horizontal
scaling
Concurrency

9. 9
The Road to 100X
Proxy
Replicas
Filtered /
Chained
Commit /
Edge
Clustering
9

10. 10
100X: Advanced Replication
DO NOT DISTRIBUTE
10
Filtered
Replication
Chained
Replicas
Git
Replication
Available Now

11. 11
100X: Remote
Site Support
11
Eliminate
WAN
traffic
for
many
opera9ons
Reduce
data
transfer
Commit
Edge
Edge

12. 12
Reduced Activity on Commit Instance
12
Replica
Master
Edge
Master

13. 13
Remote Sites: Just Faster
56.6
8.7
61
9.8
0.9
0.7
1.8
0.2
0
10
20
30
40
50
60
70
Sync
Revert
Integrate
Edit
COMMON
OPERATIONS
WITH
128MS
LATENCY
BETWEEN
CLIENT
AND
P4D
Direct
Edge

14. 14
100X: 2014
Horizontal scaling (read ops)
High availability (failover)
Concurrency

15. 15
Nuts and Bolts
Details, details, details…

16. 16
100X
FailoverCommit/edge
Chain
replicas
Horizontal
scaling
Concurrency
Filter replicas

17. 17
Chaining Replicas
17
p4
configure
set
replicaSingapore#P4TARGET=master:1666
p4
configure
set
replicaHK#P4TARGET=replicaSingapore:1666
Configuration
Use common sense
Ask for help when necessary
Master Repository
(California)
Read-Only Replica
(Singapore)
Read-Only Replica
(Hong Kong)
Read-Only Replica
(Singapore)
Read-Only Replica
(Singapore)

18. 18
Filtering Replicas
Configure in server spec
and pull commands
18
>
p4
server
repl
ServerID:
repl
RevisionDataFilter:
//gui/...
>
p4
configure
set
"repl#startup.1=pull
-­‐i
1
-­‐P
repl"
Singapore Replica
Estonia Replica
Toronto Replica 20 TB
500 GB
50 GB
Master Repository
(US)
500 TB

19. 19
Git Replication
19
Configuration
• Set P4PORT in Git Fusion
configuration to proxy, broker, or
replica
Access control
• Set IP-based rules on Git Fusion
account
FAQ
• Commits are identical across all Git
Fusion instances

20. Upgrading
to commit /
edge
DR Replica
Build Server
Replica
Versioning Service
Small Remote
Office
Large Remote Office
Proxy Service
Forwarding Replica Git Fusion
Main Office

21. Upgrading
to commit /
edge
DR
Replica
Edge Server
(for Build Farm)
Versioning Service
Small Remote
Office
Large Remote Office
Proxy
Service
Edge Server Git Fusion
Main Office
Edge Server
(for Users)

22. 22
2014: Horizontal Scaling of Read Operations
Write
Node
Read
Node
Read
Node
Read
Node
Journal
Service
Coordinator
Read Node

23. 23
Write
Node
Read
Node
Read
Node
Read
Node
Coordinator
Journal
Service
2014: High Availability and Failover

24. 24
2014: Improved Replication Throughput
Write
Node
Read
Node
Read
Node
Read
Node
Coordinator
Journal
Service
Durable
write

25. 25
100X
Advanced
replicaKon
Remote
Sites
Scaling,
failover,
and
concurrency
Perforce
Git

26. 26
Questions?
See Git Fusion in the Demo Lounge
Follow us
Randy DeFauw: rdefauw@perforce.com, @rdefauw
Charlie McLouth: cmclouth@perforce.com
P4Ideax
Forums