The Scorecard Viewer provides a high-level overview of the application's build and runtime hosts. Several aspects of the system are scored according to a three-level criteria. An overall score is also provided on Power systems.

| Icon | Meaning | Description |
|---|---|---|
![]() |
Following best practices | Best practices are being following for this aspect of the system. No action needs to be taken. |
![]() |
Following some best practices. | There may be an opportunity for some performance improvement if this aspect of the system is updated in some way. Check the recommendations. |
![]() |
Missing key best practices | A problem has been detected that could potentially be a major factor in limiting application performance. Action should be taken to remedy the situation. Check the recommendations. |
The overall score is the average of all the other scores. The overall score is only available on Power systems.
The data collected by a System Scorecard Activity is automatically analyzed and several recommendations may be generated. If there are recommendations then a link will be shown under the overall score, clicking this link will open the Recommendations View and show the recommendations.
The host where your application is built.
On Power systems, the host's hardware and Operating System levels are checked for best practices.
The host where your application is run and measured. This may be the same as the Build System host above.
On Power systems, he host's hardware and Operating System levels are checked for best practices.
If the Session was created with a non-zero percentage of Java code and the host is a Power system, then the host's Java Virtual Machines are checked for best practices.
This is the list of program executables that are stored in the Session. Many programs consist of a single executable, however some applications, such as client-server applications, may consist of multiple executables working in tandem. Each executable is analyzed according to how it was built, looking for any potential improvement to compiler versions or optimization levels.
This is the list of shared libraries that are linked with one or more of your application's executables. This list is stored in the Session. Each shared library is analyzed according to how it was built, looking for any potential improvement to compiler versions or optimization levels.
The list of executables and shared libraries is stored in the Session. The list may be entered when the Session is created. If a Hotspot Detection Activity is created and the executable is not in the list you will be prompted to add it. Additionally it is possible to manually update the list by right-clicking on a Session and selecting Configure.
