Bug 54478 - Wrong response time with mode=Statistical and num_sample_threshold > 1 when using remote mode.
Summary: Wrong response time with mode=Statistical and num_sample_threshold > 1 when u...
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.9
Hardware: PC All
: P2 regression (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-24 14:32 UTC by Eagle Liu
Modified: 2013-04-04 01:13 UTC (History)
0 users



Attachments
My test script and JTL logs (4.85 KB, application/x-zip-compressed)
2013-01-24 14:32 UTC, Eagle Liu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eagle Liu 2013-01-24 14:32:18 UTC
Created attachment 29890 [details]
My test script and JTL logs

This issue should be existed from JMeter 2.7 to latest night build [apache-jmeter-r1437941]. I have just used latest night build to reproduce this issue.

To show this problem, I compared test result with following two test case.

I used one PC to reproduce this issue.
Case A:
1. start JMeter server with jmeter-server.bat.
2. enable following two parameters in jmeter.properties
mode=Statistical
num_sample_threshold=40

3. run JMeter client with following command[NO GUI is required]:
jmeter.bat -n -r -t debug.jmx -l Statistical_40_1.jtl

Each average of Sample result in Summary Report is too large and total average response is about 5111 ms.

Case B:
1. start JMeter server with jmeter-server.bat.
2. enable following two parameters in jmeter.properties
mode=Statistical
num_sample_threshold=1

3. run JMeter client with following command:
jmeter.bat -n -r -t debug.jmx -l Statistical_1_1.jtl

Total average response is about 272 ms.

The result in Case A is unreasonable. Please fix it.
Comment 1 Eagle Liu 2013-02-15 07:15:10 UTC
duplicated with 2.9 release.