Perforce Public Knowledge Base - TRACK2SQL
× PRODUCTS SOLUTIONS CUSTOMERS LEARN SUPPORT
Downloads Company Partners Careers Contact Free Trials
Menu Search
Perforce
Reset Search
 

 

« Go Back

Information

 
Problem

I am experiencing performance problems with my Perforce Server, but I am unable to isolate the causes.

Solution

Where to find Track2SQL

Download Track2SQL, or download a Track2SQL replacement, log_analyzer.php.  These tools analyzer your server's logfile to identify problematic user commands. Examine slow commands to identify resource constraints and take action.  There used to be a Perforce Server Log Analyzer online but that is not available now,

Remove Client Workspace Locks First

Before The Perforce log may show long read or write locks on clients seen in Client Workspace and Global Metadata Locks

--- clients/bruno(W)
---   total lock wait+held read/write 0ms+0ms/215085ms+43548ms

This usually only affects the particular client and not the Perforce database.  To remove these lines, use the sed command to remove the client and meta lock line and the following line before running vtrack.py

$ cat log | sed -e '/^\-\-\- meta\/db/,+1d' -e '/^\-\-\- clients\//,+1d' > log.noclientlocks

README

https://swarm.workshop.perforce.com/files/guest/stewart_lord/track2sql/README
Related Links

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255