Oracle performance

Analyzing the results

At completion of the performance test, Forms2test will automatically generate comprehensive graphical Excel reports using the captured performance statistics and show you a Summary Report dialog. From this dialog you can open the event and error log and the generated whole test report.



The performance reports are saved to the output directory (see Settings Tab). The performance reports have the following naming convention:

Whole scenario report: forms2test_<yyyymmdd>-<hhmiss>.xls Per script reports: <script name>_<yyyymmdd>-<hhmiss>.xls

During the performance test, Forms2test captures performance statistics and error and log information to the log directory and the output directory. The output directory can be set in the settings tab. forms2test.err (log directory) This file contains a log of errors that might be useful for problem determination. This log is stored in the form of a text file. An error log entry has the following format:

[timestamp] [script name]([session id]) [user action]: [log message]

Example entry:

7-dec-2006 21:20:36 script(0_26) Database log on: ORA-12516: TNS: listener could not find available handler with matching protocol stack

This entry means that the user session identified by “0_26” (the 27th user session) for script “script” received database error ORA-12516 during the execution of user action “Database log on”.

forms2test.log This file contains runtime information about events during the test scenario. It shows among others the session startups, database and forms messages, runtime parameter values, etc. A log entry is similar to the error log

Example entry:

7-dec-2006 21:19:58 script(0_1) Querying data: FRM-40100: at first record

This entry means that user session identified by "0_1" (the 2nd user session) for script "script" received Forms message FRM-40100 during the execution of user action "Quering data".

forms2test.csv (output directory) - this file contains whole scenario performance statistics captured by Forms2test every five seconds during the test. This file is in a comma-separated values (CVS) format and can be imported into a spreadsheet directly.

<script name>.cvs (output directory) - Besides the whole scenario performance statistics Forms2test captures also the performance statistics for each script. This file is also in a comma-separated values (CVS) format and contains the same metrics as the whole scenario performance metrics, but also the performance statistics for each user action.

The script reports also contain graphical performance results for each transaction. For a transaction the following statistics are available:

• Baseline response time (in milliseconds)
• Minimum response time during the test (in milliseconds)
• Maximum response time during the test (in milliseconds)
• Average response time during the test (in milliseconds)

The following example report shows the statistics for a transaction. The average response time of all network requests within a transaction is above the baseline response time, the maximum response time increased during the test and the minimum response time decreased. At completion of the test scenario, Forms2test will automatically generate comprehensive graphical Excel reports using the captured performance statistics and show you a Summary Report dialog. From this dialog you can open the event and error log and the generated whole scenario report.