The Active Console, like any Java application, can be profiled using the inbuilt profiler in the JDK.
This page describes the basics of how to do this. NOTE that in this article at least we are assuming you are using Windows.
Performing Rudimentary Profiling
1) The first step is to download and install the Java SDK
2) Once installed go to the installation directory (example shown below), and run the following exe
This will run up the profiler.
3) Next start the console via its activeconsole.exe as normal, inside the VisualVM a new process will appear, called 'Local Application'
If you double click on the 'Local Application' it will start doing rudimentary profiling of the Active Console. Clicking on the 'Monitor' and 'Threads' tabs will show you the memory and CPU foot print of the application and the threads (many of which are JAVA threads, rather than being Console specific code).
Understanding the results
The metrics of most interest at the rudimentary level are the CPU and memory footprints of the Active Console.
CPU: If the CPU is running high over an extended period of time, then its probably indicative of a loaded console. Note that high is equal to 100% / numcpus. So, for example, if your PC has 4 cores, then the Console running on or near 25% would be highly loaded. You can review the FAQ on Managing Load in Geneos to try and track down specifics.
Memory: The console has two parts to its total memory footprint on the PC, a C++ component, and a JAVA component. If you look in the Task manager you will see the some of these. The profiler however will only show you the JAVA memory foot print, an example of which is shown below.
There are a number of features in these charts that are of note:
1) they will be of a saw tooth shape, this is normal for any JAVA application, as memory is used and reclaimed buy garbage collects