Presentation - Perforce

More documents

Recommendations

Info

NON-PERFORMANCE ISSUES OF SCALE • Depot disk space • Checkpoints • High availability • Administrative load
DEPOT DISK SPACE • Ways of cleaning up disk space: • obliterating • stubbing out files (http://kb.perforce.com/article/72 /making-large-repositories-smaller) • moving to less expensive storage with archive depots and p4 archive and p4 restore, as of <strong>Perforce</strong> 2010.2 • replacing multiple identical files with hard links • Use +S modifier with care • +S only saves the most recent version(s) of file • But branched copies of +S files arent lazy copies • So if a file is branched a lot, +S can make it take up more space. Possibly a lot more.
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: Non-Performance Issues of Scale
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?