https://issues.apache.org/bugzilla/show_bug.cgi?id=57346

            Bug ID: 57346
           Summary: Summariser : The + reports wrong "in" and as impact
                    computes wrond throughput
           Product: JMeter
           Version: 2.12
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: [email protected]
          Reporter: [email protected]

Hello,
We have a test with and average of 155 to 160 req/s.

Summariser is configured to display every 10s:
summariser.name=summary
# interval between summaries (in seconds) default 3 minutes
summariser.interval=10
# Write messages to log file
summariser.log=true
# Write messages to System.out
summariser.out=true

It shows the following:
summary +   1597 in   591s =    2.7/s Avg:   276 Min:     0 Max: 18732 Err:    
0 (0.00%) Active: 3024 Started: 3024 Finished: 0
summary = 1372439 in  8683s =  158.1/s Avg:   316 Min:     0 Max: 32952 Err:   
 3 (0.00%)
summary +   1676 in   580s =    2.9/s Avg:   250 Min:     0 Max: 18193 Err:    
0 (0.00%) Active: 3024 Started: 3024 Finished: 0
summary = 1374115 in  8693s =  158.1/s Avg:   316 Min:     0 Max: 32952 Err:   
 3 (0.00%)
summary +   1640 in   591s =    2.8/s Avg:   326 Min:     0 Max: 20648 Err:    
0 (0.00%) Active: 3024 Started: 3024 Finished: 0
summary = 1375755 in  8703s =  158.1/s Avg:   316 Min:     0 Max: 32952 Err:   
 3 (0.00%)
summary +   1552 in   589s =    2.6/s Avg:   344 Min:     0 Max: 19179 Err:    
0 (0.00%) Active: 3024 Started: 3024 Finished: 0
summary = 1377307 in  8713s =  158.1/s Avg:   316 Min:     0 Max: 32952 Err:   
 3 (0.00%)



As you can see, summary throughtput is OK while interval throughput is wrong:
It says 589s instead of 10s
It computes 2.6/s to 2.9/s due to the time interval.
If it had divided by 10 throughput would be OK.

Issue affects all version of JMeter from 2.6 to 2.12

Regards
@ubikloadpack

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to