Benchmark test analysis example
Output from a benchmark testing program should include an identifier for each test, iteration numbers, statement numbers, and the elapsed times for each execution.
Note that the data in these sample reports is shown for illustrative purposes only. It does not represent actual measured results.
A summary of benchmark testing results might look like the following:
Test Iter. Stmt Timing SQL Statement
Numbr Numbr Numbr (hh:mm:ss.ss)
002 05 01 00:00:01.34 CONNECT TO SAMPLE
002 05 10 00:02:08.15 OPEN cursor_01
002 05 15 00:00:00.24 FETCH cursor_01
002 05 15 00:00:00.23 FETCH cursor_01
002 05 15 00:00:00.28 FETCH cursor_01
002 05 15 00:00:00.21 FETCH cursor_01
002 05 15 00:00:00.20 FETCH cursor_01
002 05 15 00:00:00.22 FETCH cursor_01
002 05 15 00:00:00.22 FETCH cursor_01
002 05 20 00:00:00.84 CLOSE cursor_01
002 05 99 00:00:00.03 CONNECT RESET
Analysis shows that the CONNECT (statement 01) took 1.34 seconds to complete, the OPEN CURSOR (statement 10) took 2 minutes and 8.15 seconds, the FETCH (statement 15) returned seven rows, with the longest delay being 0.28 seconds, the CLOSE CURSOR (statement 20) took 0.84 seconds, and the CONNECT RESET (statement 99) took 0.03 seconds to complete.
If your program can output data in a delimited ASCII format, the data could later be imported into a database table or a spreadsheet for further statistical analysis.
A summary benchmark report might look like the following:
PARAMETER VALUES FOR EACH BENCHMARK TEST
TEST NUMBER 001 002 003 004 005
locklist 63 63 63 63 63
maxappls 8 8 8 8 8
applheapsz 48 48 48 48 48
dbheap 128 128 128 128 128
sortheap 256 256 256 256 256
maxlocks 22 22 22 22 22
stmtheap 1024 1024 1024 1024 1024
SQL STMT AVERAGE TIMINGS (seconds)
01 01.34 01.34 01.35 01.35 01.36
10 02.15 02.00 01.55 01.24 01.00
15 00.22 00.22 00.22 00.22 00.22
20 00.84 00.84 00.84 00.84 00.84
99 00.03 00.03 00.03 00.03 00.03