You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2018/01/03 18:43:43 UTC
[Bug 61962] New: Latency Vs Request graph does not exceed 1000 RPS
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Bug ID: 61962
Summary: Latency Vs Request graph does not exceed 1000 RPS
Product: JMeter
Version: 3.2
Hardware: Macintosh
OS: other
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: miccah.castorina@ibm.com
Target Milestone: ---
Created attachment 35645
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35645&action=edit
"Hits Per Second" and "Latency Vs Request" graphs
This issue related to the JMeter report generation.
We are running tests where we are getting "Hits Per Second" and "Transactions
Per Second" reaching 2000, but the "Latency Vs Request" graph and "Response
Time Vs Request" graph never exceed 1000 RPS.
See attachment for "Hits Per Second" and "Latency Vs Request" graphs.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #13 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello,
Issue should be fixed now, you can download in few minutes a working build:
http://jmeter.apache.org/nightly.html
Use jenkins link and download zip (non source)
Regards
Philippe M.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #15 from miccah.castorina@ibm.com ---
Confirmed this is now fixed.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Sungjin Yook <su...@us.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request and Response Time Vs Request graphs
do not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Latency Vs Request graph |Latency Vs Request and
|does not exceed 1000 RPS |Response Time Vs Request
| |graphs do not exceed 1000
| |RPS
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #10 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
(In reply to miccah.castorina from comment #9)
> Thank you for the insights, but I don't believe those properties are the
> issue.
> I downloaded a fresh copy of jmeter-3.2, changed the below two properties,
> and the resulting graphs are the same.
>
> jmeter.save.saveservice.timestamp_format=dd/MM/yyyy HH:mm:ss zzz
> jmeter.reportgenerator.overall_granularity=1000
Ok, thanks, I'll investigate issue further in the upcoming days.
>
> Yes, each thread group is uniquely identified by its IP, and for this test
> we are only using one jmeter server with multiple workers.
>
> To answer your questions about customization, we were running into an issue
> where nothing was showing up in the report. We found setting
> jmeter.reportgenerator.sample_filter=.*
> jmeter.reportgenerator.exporter.html.series_filter=.*
> fixed that problem.
The correct way is to follow my previous advice.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Author: pmouawad
Date: Thu Jan 4 23:16:21 2018
New Revision: 1820239
URL: http://svn.apache.org/viewvc?rev=1820239&view=rev
Log:
Bug 61962 - Latency Vs Request graph does not exceed 1000 RPS
Contributed by UbikLoadPack
Bugzilla Id: 61962
Modified:
jmeter/trunk/src/core/org/apache/jmeter/report/processor/graph/AbstractVersusRequestsGraphConsumer.java
jmeter/trunk/xdocs/changes.xml
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #3 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Also are you using distributed testing ?
Thank you
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #8 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello,
Thanks for provided information.
Can I ask you to summarize what you customized ?
Usually properties should only be overriden in user.properties and
jmeter.properties/reportgenerator.properties should not be touched.
I suspect that the following settings might be a cause of your problem:
jmeter.reportgenerator.exporter.html.filters_only_sample_series=false
jmeter.reportgenerator.sample_filter=
Why did you change them ?
To filter samplers, just use jmeter.reportgenerator.exporter.html.series_filter
and use Menu Help > Export Transactions for report
Also, if using 3.3, you don't need to set this unless you have an external
process that uses csv file generated by JMeter
jmeter.save.saveservice.autoflush=true
Ensure you read :
http://jmeter.apache.org/usermanual/generating-dashboard.html#configuration_requirements
Can you confirm you followed this:
--------------------------------------------------------
When using JMeter distributed mode with multiple jmeter-server instances,
ensure you add in your Thread Groups something that uniquely identifies
ThreadGroup for every JVM, example:
ThreadXXX_${__P(JVM_ID)}
where you pass a different JVM_ID property for each jmeter-server through:
-JJVM_ID=i
where i varies between 1 and the number of jmeter-server you are using.
--------------------------------------------------------
I'll investigate further following your answers.
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |p.mouawad@ubik-ingenierie.c
| |om
--- Comment #2 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello,
Would it be possible to provide a short CSV file +
user.properties+jmeter.properties so that we have a reproducer ?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #11 from Sungjin Yook <su...@us.ibm.com> ---
I am also closely monitoring this thread. Our Jmeter master and slaves are NTP
time sync'ed on our kubernetes cluster. I tried stock 3.3 Jmeter without
modification, saw that RPS falls behind hits/sec. Test was done locally on my
laptop and wasn't distributed tests. Thanks in advance working on this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |major
Version|3.2 |3.3
Hardware|Macintosh |All
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #1 from Sungjin Yook <su...@us.ibm.com> ---
I observed same bug. In web report, I have high number of hits/sec (i.e. 2000
hits/sec) but "Latency vs RPS graph"'s x-axis only goes up to ~1000 RPS.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #6 from miccah.castorina@ibm.com ---
Created attachment 35653
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35653&action=edit
Example user.properties
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #5 from miccah.castorina@ibm.com ---
Created attachment 35652
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35652&action=edit
Example jmeter.properties
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #14 from Sungjin Yook <su...@us.ibm.com> ---
@Philippe
I am really impressed with fast response on this issue.
Will test out on the cluster tomorrow and update.
Thanks again for your effort and time on this !
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #4 from miccah.castorina@ibm.com ---
Created attachment 35651
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35651&action=edit
Example CSV File (40K samples)
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #9 from miccah.castorina@ibm.com ---
Thank you for the insights, but I don't believe those properties are the issue.
I downloaded a fresh copy of jmeter-3.2, changed the below two properties, and
the resulting graphs are the same.
jmeter.save.saveservice.timestamp_format=dd/MM/yyyy HH:mm:ss zzz
jmeter.reportgenerator.overall_granularity=1000
Yes, each thread group is uniquely identified by its IP, and for this test we
are only using one jmeter server with multiple workers.
To answer your questions about customization, we were running into an issue
where nothing was showing up in the report. We found setting
jmeter.reportgenerator.sample_filter=.*
jmeter.reportgenerator.exporter.html.series_filter=.*
fixed that problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61962] Latency Vs Request graph does not exceed 1000 RPS
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61962
--- Comment #7 from miccah.castorina@ibm.com ---
Philippe,
I've added the files you requested to the attachments. The CSV file is the same
from the attached image truncated to 40K samples.
Yes this is using distributed testing.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.