<p><imgsrc="../images/processcontroller-images/applet.png"alt="ProcessController applet"style="float:left;margin: 0 1em 0 0"/>The primary task of the ProcessController applet is to show the activity of your CPU(s) and the amount of used memory. It allows monitoring of individual teams, change their priority, and kill them if the program freezes. In multiprocessor environments it allows you to disable individual processors/cores. When Tracker or Deskbar crash you can restart them from ProcessController's menu.</p>
<p>Indicators on the left show each CPU's usage, while the bar on the right shows the memory consumption. Remember that the number of indicators depend on the number of processors/cores in the computer.</p>
<p>If not yet running, launching ProcessController asks if it should open in window mode or live in the Deskbar. In window mode you can resize the bar-display by resizing the window and then use the <ahref="../gui.html#replicants">Replicant</a> handle to drag it to the Desktop.<br/>
<p>To quit an application just choose its name from the <spanclass="menu">Quit an application</span> menu. This is a clean way to close app, just like clicking its close button. Be careful not to quit system processes like servers or daemons, however. Your system may stop working reliably. </p>
<p>Monitoring memory usage can be rather inaccurate.</p>
<p>This menu allows you to monitor memory usage of different teams in your system. Next to the team's name there are two columns: first with the amount reserved for writable memory, while the second shows all memory including read-only space (shared libraries for example).</p>
<p>The first row <i>System resources & caches...</i> shows the total amount of memory used by the system and all applications. The length of the blue bar is based on the total physical memory in your computer. The next rows show memory used by each process. Note that the length of the bar is based only on the actually used part of the memory.</p>
<tr><tdstyle="width:20px;height:20px;background:#1414E7"></td><tdstyle="width:10px"></td><td>Memory used only by given application (with write access)</td></tr>
<tr><tdstyle="height:20px;background:#A4A4F5"></td><td></td><td>Memory including read-only space (can be shared with other applications)</td></tr>
<p>This menu allows you to change thread priorities, kill teams or debug them.</p>
<divclass="box-stop">Changes via the commands in this menu reach deep into the system and can cause data loss and system instability. Keep that mouse hand steady!</div>
<p>At the first level you see team names. By clicking on one, you can kill the whole team. The dark-blue part of the bar is time spent in kernel code, the light-blue part in user code, the green part in the idle thread(s). A bar completely filled with blue means that the team is using all processoring power.</p>
<p>The second level shows particular threads of a team. By clicking on one, you can debug or kill it. A bar completely filled with blue means that the thread is pegging one processor/core.</p>
<p>The last level of the menu allows you to change a thread's priority. Be careful with that! As a rule of thumb the priority of a thread should be inverse its CPU usage. That is, the more it tries to claim CPU time, the lower should be it's priority. In general, don't mess with an app's priorities; contact its author, that's his business.
