Displaying the Performance Test Results


After you have conducted a performance test using ST30 you can view the test results on the Data Overview tab. The Analysis tab provides you with an additional overview of the information you obtained through an analysis of the test results.


Displaying the Performance Figures

There are two locations where you can view the performance figures of a performance test: on the Data Overview tab in ST30, and in transaction ST33.

The information displayed on the Data Overview tab is identical to that provided in the Aggregated Performance Data for Each Performance Test view in transaction ST33. In addition, ST33 contains other performance figures in a raw (non-aggregated) format.

To view the performance figures in transaction ST33 proceed as follows:

       1.      Select and display the performance test by specifying the relevant selection criteria, such as log ID, logon name of user etc.

       2.         Double-click on the performance test to call a list from which you can select detailed performance data.

       3.         Double-click on the type of information you are interested in, for example, RFC trace data. The system displays the details for your performance test.

For example, choosing the report SQL Trace Data (Tables) will display the following performance figures:

¦       Table Name

¦       Abbreviated SQL Statement

¦       Number of Database Accesses

¦       Total number of Database Records Passed

¦       Total Runtime of SQL Statements

Displaying the Analysis Results

On the Analysis tab in ST30 you can see the analysis results (of Code Inspector checks and the programming guidelines checklist, if used) obtained through a performance test.

You can also view the analysis results of a performance test carried out previously. To do so, specify the test in the Performance Test field, then load the results with Read Results.

The Analysis tab consists of two main sections where different analysis results are displayed:

Analysis Results Overview: Messages per Destination

The data that you see here is derived from the Code Inspector and is only available if you set the following indicators in the eCATT Test tab before you run the performance test:

?      SQL Trace Analysis (and also With Run from SQL Trace)

The overview information coming from this function is displayed in the SQLErrors, SQLWarnings, and SQLInformation columns.

?      Static Program Analysis (and also With Run from SQL Trace)

The overview information coming from this function is displayed in the StaErrors, StaWarnings, and StaInformation columns.

Each line provides only a brief overview of the test results, such as how many errors were found in the SQL statements that were executed. To obtain detailed information, select a line and choose SQL Trace Analysis or Stat. Program Analysis. This will take you directly to the respective screen in the Code Inspector in the system where the performance test was running. The Code Inspector allows you to drill down to the level of individual messages and, if applicable, also to the line in the program coding where the performance problem originates.

Read the documentation provided for each performance problem category to find out more about the nature of the problem.

Programming Guidelines Checklist

The status information displayed in the Appropriate Indexes, Complete WHERE clauses, and Buffers and Caches columns is derived from the Code Inspector. The status information in the other columns is derived from the statistics data and the SQL trace.

Status information is only available if you set the following indicator in the eCATT Test tab before you run the performance test:

?      Checklist

The creation of the checklist is only possible if SQL Trace Analysis and therefore also With Run for SQL Trace were activated at the same time.

The results of the checklist generated here can be transferred directly to an external spreadsheet application, such as Microsoft Excel, using copy and paste.

For more information see Running eCATT Test Configurations from Within ST30.