Presentation - Perforce

More documents

Recommendations

Info

CONFIGURABLES • Configurables allow some low-level tuning. • Only use with advice from Perforce product support. • Introduced and evolved in Perforce 2008.2 through 2010.2. Originally called tunables. • For more information see p4 help configurables and Perforce Tunables, http://www.perforce.com/perforce/conferences/eu/2010/ Presentations/Michael_Shields-Tunables.paper.pdf (Michael Shields, 2010)
MONITORING • Monitoring is an essential part of maintaining any service, Perforce or otherwise. • Monitoring can page, send email, or create bug reports, depending on the severity of the problem. • The goal is never to be notified about a problem by one of your users. • Performance-specific monitoring at Google: • commands holding long-running locks (locks.pl, in the Perforce Public Depot in //guest/dan_bloch/) • commands using more than 3 GB of memory • users running many commands in parallel
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: THE EASIEST WAY TO IMPROVE PERFORMA
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

Create successful ePaper yourself

Delete template?

Save as template?