The System Information heading lists details of EASA's resource footprint, by default this includes
Additional system resource values can be configured for display under System Information by making use of Performance Logs defined in the Computer Management tool available in Windows. See Adding a System Resource Monitor Value for details.
The Server Output page provides diagnostic messages from the EASA Server.
Many of the messages are time and date stamped to help track down when and why problems may have occurred on an EASA system.
The output from the Tomcat HTTP server (HTML localhost:80) is also available from this page, access it via the radio buttons above the log window.
On the Logging page, set the level or quantity of logging performed by EASA, stored in the server.txt file and displayed on the Server Output page.
This table lists all the system commands currently being run by EASA. These typically are associated with submitted EASAP processes being run either locally on the EASA Server acting as a Compute Server or via rsh commands to a remote Compute Server.
Press the Free Resources button to free up computer memory that the EASA Server no longer needs. 'Before' and 'after' memory usage is displayed.
EASA uses many threads though the roles of each are not in the scope of this document.
All Threads shows the current status for all EASA threads.
Memory is freed up automatically, from time to time.
In addition to the default system resource values displayed on the Summary page under the Diagnostics selection, it is possible to monitor additional system resources by making use of Performance Logs defined in the Computer Management tool available in Windows.
Unlike in Windows XP, Counter Logs in Windows 7 are organized into Data Sets. To create a new Counter Log in Windows 7, please follow these instructions.
The log file is stored in the root folder.
easa.server.systemmonitor1=C\:/PerfLogs/cpu.csv,2,% CPU Time easa.server.systemmonitor2=C\:/PerfLogs/mem.csv,2,RAM Usage