Preview the problem and solutions that prompted RIM's presentation by Shannon Mann

1. Extending
Perforce
Scalability
Using
Job
Content
Synchronization
Shannon
Mann,
RIM
ABOUT THE PRESENTATION
Problem: What motivated you to do the work you will describe in this presentation?
During planning for a split, we determined that our bug-tracking integration would not scale to multiple depots
Solution: How did you solve the problem?
We abstracted the relationship between Perforce and the bug-tracking system (connected via P4DTG) into a
'virtual' system by putting a jobs-only depot between production depots and the bug-tracking system.
ABOUT YOUR SOLUTION
To which users and/or tasks is your solution relevant?
The solution allows near linear scalability between a bug-tracking system and as many depots as you want to
connect. This helps splits or anyone wanting to share a bug-tracking system between multiple depots.
How long has your solution been deployed?
Seven Months
What programming languages and/or software development tools did you use to develop your solution?
Bourne Shell for the trigger. Python for automation assistance.
Which Perforce tools and/or APIs did you use?
We used P4DTG, P4Change, P4Auth and P4Broker. P4Python was used to automate some testing and data
manipulation.
On what hardware/OS/configuration is your solution deployed?
Originally, Sun X4600, 8 quad-core Opteron CPUs, 256 GBytes RAM running Linux 2.6 with Perforce 2009.2.
Now, IBM x3950X5, 8 Hex-core Xeon CPU's, 384 GBytes RAM running Linux 2.6 with Perforce 2010.2.
Depot data resides on SAN and metadata on SSD-based SAN.
What other software or hardware does your solution depend on?
An optional part uses Oracle DB to track changelist-to-depot mappings.
Full presentation available at slideshare.net/perforce.