Presentation - Perforce

More documents

Recommendations

Info

REDUCING METADATA • Less data to scan means faster commands. • Even in cases where it doesnt, it means faster checkpoints, and money saved on expensive storage. • This reduction can be approached both reactively (cleanups) and proactively (strategies to create less metadata). • This only applies to metadata. Less depot content doesnt improve performance.
REDUCING METADATA - SPECIFICS • Client and label cleanups – straighforward. Beneficial, but not a performance benefit. • Sparse clients: Ideally, users only need to sync the directories theyre editing. • Some build systems provide support for this, e.g. gnumakes vpath functionality. • Google uses a proprietary file system integration. • Sparse branches: Small branches with most of the content coming from the mainline. More valuable: Clients are temporary, but branches are forever. • <strong>Perforce</strong> provides some support: overlay mappings (http://kb.perforce.com/article/890/sparse-branching) • Google also has a build integration to specify the mainline changelist level.
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: MONITORING, CTD. • Killing proces
Page 23 and 24: OFFLOADING WORK FROM PERFORCE • R
Page 25 and 26: Non-Performance Issues of Scale
Page 27 and 28: DEPOT DISK SPACE • Ways of cleani
Page 29 and 30: CHECKPOINT ENHANCEMENTS • We opti
Page 31 and 32: ADMINISTRATIVE LOAD • Make all of
Page 33 and 34: LESSONS LEARNED • Know as much as

Presentation - Perforce

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?