Extending	  Perforce	  Scalability	  Using	  Job	                                                          Content	  Synch...
Upcoming SlideShare
Loading in …5
×

Fact Sheet: Shannon Mann, RIM

441 views
387 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
441
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Fact Sheet: Shannon Mann, RIM

  1. 1. Extending  Perforce  Scalability  Using  Job   Content  Synchronization   Shannon  Mann,  RIM  ABOUT THE PRESENTATIONProblem: 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 depotsSolution: How did you solve the problem?We abstracted the relationship between Perforce and the bug-tracking system (connected via P4DTG) into avirtual system by putting a jobs-only depot between production depots and the bug-tracking system.ABOUT YOUR SOLUTIONTo 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 toconnect. This helps splits or anyone wanting to share a bug-tracking system between multiple depots.How long has your solution been deployed?Seven MonthsWhat 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 datamanipulation.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 CPUs, 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.

×