The table below lists up to 25 problematic commands. These operations are likely to have degraded server performance by holding database locks for extended periods of time. When a process holds database locks (especially exclusive locks) it has the potential to block other operations and make the server less responsive.
These commands are sorted in descending order by the compute column. The compute column is an estimate (in seconds) of how long each command held locks on one or more database tables while performing work. The times are adjusted to account for idle time spent waiting for locks.
The user column contains the name of the user that issued the command. The command column shows the operation performed. The CPU column lists the user and system cpu times (in seconds), respectively. Please note, CPU time is not reported on Windows servers. The I/O column shows the volume of database disk activity (in gigabytes) separated into reads and writes respectively.
Click on each row to get detailed information about the command, such as when it was issued and what arguments were used. If possible, use this information to identify why the command was problematic and take corrective action. For example: upgrade system resources, upgrade Perforce, or tune parameters such as maxlocktime, maxresults and maxscanrows.
If you need help interpreting these results, please contact support.
{% for table in tables %}