Thread Information (SUP0014)
The greater the number of Tests running concurrently, the greater the processor load. If too many Tests are carried out at one time, a large number of software controlling threads will be trying to run, the processor may be unable to cope and data corruption may occur. Knowing the number of software threads running and having a visual indication of their approximate load is extremely useful as it will give an indication of the capabilities of the system configuration in use.
To see the number of threads running, click on the ‘Settings’ menu option and then ‘Performance’ from the drop-down menu (Figure 1).
Figure 1 - Performance Panel
The number of threads in use is displayed as a gauge to illustrate performance. The exact thread count can be seen on the lower section of the gauge (Figure 2)
Figure 2 - Thread Count Gauge
The ‘Threads’ indication light should remain grey in colour (Figure 3). Hovering over it will provide further information (Figure 3). If it starts flashing red, the load is becoming too much for the processor and one or more Tests should be closed.
Figure 3 - 'Threads' Indication LED
When opening the Performance Tab additional information alongside the Thread Count will be provided by Clisp to assist the User with monitoring performance.
This refers to the display memory assigned by the Windows Operating System. Essentially, the more screens that are open, the higher the usage. As Clisp Studio allows the User to have multiple screens open (visible or not), this can lead to similar problems as having a high thread count. To avoid this, display only what is required.
Figure 4 - Windows Resources
This refers to the data memory assigned by Windows Operating System. Similarly, an excess of open tests can overload the PC. Clisp Studio is continually using and releasing some of that memory but if not careful the same problem can occur.
Figure 5 - Memory Usage
A pdf version of this document is available, click here to download