DO NOT REPLY [Bug 48889] New: Wrong response time with mode=Statistical and num_sample_threshold > 1
[email protected] Thu, 11 Mar 2010 09:49:37 +0000 (UTC)
| Newsgroups | gmane.comp.jakarta.jmeter.devel |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://issues.apache.org/bugzilla/show_bug.cgi?id=3D48889
Summary: Wrong response time with mode=3DStatistical and
num_sample_threshold > 1
Product: JMeter
Version: 2.3.4
Platform: PC
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: Main
AssignedTo: [email protected]
ReportedBy: [email protected]
I=E2=80=99ve got a master-slave setup and need to do statistical sampling b=
ecause
otherwise the master dies on OutOfMemory. I use an Aggregate Graph/Report as
recommended. The calculated values for hits/sec reported by the listeners a=
re
wrong.
To analyze the situation use I the following testplan:
- Threadgroup with 10 threads running for 100 iterations
- BeanShell Sampler sleeping for 500 millis
- AggregateGraph/Report
Now the results must be more or like:
- Hits/sec just below 20 (like 19.6)
- Average response time approx 500 millis
Local execution delivers this result.
Set num_sample_threshold=3D1 and time_threshold=3D3600 delivers this result.
Set num_sample_threshold=3D100 time_threshold=3D3600 delivers
- Hits/sec 19.7
- Average response time 56!
The response time varies with the sample_threshold but always is way to low.
The higher the sample_threshold the higher the delta between real and repor=
ted
response time
--=20
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=3De=
mail
------- You are receiving this mail because: -------
You are the assignee for the bug.=