analyzeLog.html #1

{% extends "base.html" %}

{% block content %}

<div id=psla class=analyze>

 <h1>Perforce Server Log Analyzer</h1>

 <h2>Analyze Server Log: '{{ LogFile }}'</h2>

 <p>
  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.
 </p>

 <p>
  These commands are sorted in descending order by the <b>compute</b> column.
  The <b>compute</b> 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.
 </p>

 <p>
  The <b>user</b> column contains the name of the user that issued the command.
  The <b>command</b> column shows the operation performed. The <b>CPU</b>
  column lists the user and system cpu times (in seconds), respectively. Please
  note, CPU time is not reported on Windows servers. The <b>I/O</b> column
  shows the volume of database disk activity (in gigabytes) separated into
  reads and writes respectively.
 </p>

 <p>
  <b>Click on each row to get detailed information about the command</b>,
  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.
 </p>

 <p>
  If you need help interpreting these results, please
  <a mailto='support@perforce.com'>contact support</a>.
 </p>

    {% for table in tables %}
        <h2>{{titles[loop.index]}}</h2>
        {{ table|safe }}
    {% endfor %}

</div>

{% endblock %}