11.

К оглавлениюB0F8O.php" style="padding:2px; font-size: 14px;">1 2 3 4 5 6 7 8 9 10 11 12 

An aggregated set of statistics has been calculated based on the details collected during the course of a Benchmark run. An aggregated set of information is calculated for each script in the Benchmark run.

The main results are:

Average response time: The average response time for all dialog steps.

Weighted average response time:  All response times are divided with the expected response time, and an average is calculated.

Main lines: The execution of all steps marked with the line indicator checkbox.

Lines per hour: The throughput.

Figure 18: Aggregated stats shows an example of a simple Benchmark run. The script used is sales order, the average response time is 278.76 milliseconds, and the weighted response time is 170.57. The Weighted Response Time should be below 1000, other wise the average response time weight, according to expected response time, is too high. The throughput of the test is 5000 lines per hour.

@%20=58725AB5=.files/image018.jpg">

Figure 18: Aggregated stats

Detailed information for each step is available on the tab page “details”, see Figure 19: Detailed statistics. For each executed step, the minimum, average, and maximum response time is calculated. Also the statistical deviation is calculated. The deviation can give a signal if a locking problem has occurred during that step. The higher deviation relative to the response time, the higher the possibility that locking has occurred. Also if the maximum response time is much higher than the average, it might be an indication of locking problems.

@%20=58725AB5=.files/image019.jpg">

Figure 19: Detailed statistics

 

An aggregated set of statistics has been calculated based on the details collected during the course of a Benchmark run. An aggregated set of information is calculated for each script in the Benchmark run.

The main results are:

Average response time: The average response time for all dialog steps.

Weighted average response time:  All response times are divided with the expected response time, and an average is calculated.

Main lines: The execution of all steps marked with the line indicator checkbox.

Lines per hour: The throughput.

Figure 18: Aggregated stats shows an example of a simple Benchmark run. The script used is sales order, the average response time is 278.76 milliseconds, and the weighted response time is 170.57. The Weighted Response Time should be below 1000, other wise the average response time weight, according to expected response time, is too high. The throughput of the test is 5000 lines per hour.

@%20=58725AB5=.files/image018.jpg">

Figure 18: Aggregated stats

Detailed information for each step is available on the tab page “details”, see Figure 19: Detailed statistics. For each executed step, the minimum, average, and maximum response time is calculated. Also the statistical deviation is calculated. The deviation can give a signal if a locking problem has occurred during that step. The higher deviation relative to the response time, the higher the possibility that locking has occurred. Also if the maximum response time is much higher than the average, it might be an indication of locking problems.

@%20=58725AB5=.files/image019.jpg">

Figure 19: Detailed statistics