Presentation - Perforce

More documents

Recommendations

Info

CHECKPOINTS • Checkpointing methods: • normal checkpoint – server is unavailable • offline checkpoints – create a duplicate database from checkpoint + journal, and checkpoint that • Logical Volume Manager (LVM) checkpoints • Having tried all the variants, Google currently uses LVM snapshot checkpoints. • See Demystifying <strong>Perforce</strong> Backups and Near Real- Time Replication, http://www.perforce.com/perforce/ conferences/eu/2008/presentations/ perforce_richard_baum_whitepaper.pdf (Richard Baum, 2008)
CHECKPOINT ENHANCEMENTS • We optimize our checkpoints and restores by processing each database file individually, so we can checkpoint and install multiple database files in parallel. • We checkpoint the standbys at the same time as the main server, so we have a checkpoint even if one job fails.
Page 1 and 2: Still All on One Server: Perforce a
Page 3 and 4: OVERVIEW • Perforce at Google •
Page 5 and 6: PERFORCE AT GOOGLE • Almost all o
Page 7 and 8: SUBMITS PER MINUTE • Bullet text
Page 9 and 10: Performance
Page 11 and 12: PERFORCE METADATA • There are abo
Page 13 and 14: MACHINE RESOURCES • CPU - general
Page 15 and 16: THE EASIEST WAY TO IMPROVE PERFORMA
Page 17 and 18: MONITORING • Monitoring is an ess
Page 19 and 20: MONITORING, CTD. • Killing proces
Page 21 and 22: REDUCING METADATA - SPECIFICS • C
Page 23 and 24: OFFLOADING WORK FROM PERFORCE • R
Page 25 and 26: Non-Performance Issues of Scale
Page 27: DEPOT DISK SPACE • Ways of cleani
Page 31 and 32: ADMINISTRATIVE LOAD • Make all of
Page 33 and 34: LESSONS LEARNED • Know as much as

Presentation - Perforce

Create successful ePaper yourself

Delete template?

Save as template?