Presentation - Perforce

More documents

Recommendations

Info

PERFORMANCE WORK • Background: database locking and concurrency • Machine resources • <strong>Perforce</strong>, Inc. improvements • Configurables • Monitor and if necessary, kill user commands • Reducing metadata • Offload work from <strong>Perforce</strong> • Multiple servers - maybe
PERFORCE METADATA • There are about thirty-five database files, with names like db.have, db.labels, db.counters, etc. • Details about the schema can be found at http://www.perforce.com/perforce/r10.2/schema/index.html • Information about specific db files is in my white paper.
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: Performance
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 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?