Bug 62883

Summary:	Report / Dashboard : Change the way percentiles are computed for Response Time Percentiles Over Time (successful responses) graph
Product:	JMeter - Now in Github	Reporter:	Philippe Mouawad <p.mouawad>
Component:	Main	Assignee:	JMeter issues mailing list <issues>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	p.mouawad
Priority:	P2	Keywords:	FixedInTrunk
Version:	5.0
Target Milestone:	JMETER_5.1
Hardware:	All
OS:	All

Description Philippe Mouawad 2018-11-04 13:43:25 UTC

As per discussion on mailing list:

- http://mail-archives.apache.org/mod_mbox/jmeter-dev/201811.mbox/%3CCAH9fUpafHR9kYanVRP2iJ7wyKEDOFYUrBPi9gBOZ%3DdFyeemDZw%40mail.gmail.com%3E

In summary:

Currently when we compute percentiles for this graph, for each time slot of a granularity we start the percentile computing from previous slot data:
https://github.com/apache/jmeter/blob/trunk/src/core/org/apache/jmeter/report/processor/PercentileAggregator.java#L53

Which leads to such result:

    https://ibb.co/mT22YL

This is weird because Max should be higher than Percentile

If we start for each time slot from blank:

    https://ibb.co/nJiWSf

Comment 1 Philippe Mouawad 2018-11-04 13:50:52 UTC

Author: pmouawad
Date: Sun Nov  4 13:49:37 2018
New Revision: 1845737

URL: http://svn.apache.org/viewvc?rev=1845737&view=rev
Log:
Bug 62883 - Report / Dashboard : Change the way percentiles are computed for Response Time Percentiles Over Time (successful responses) graph
Bugzilla Id: 62883

Modified:
    jmeter/trunk/src/core/org/apache/jmeter/report/processor/PercentileAggregator.java
    jmeter/trunk/xdocs/changes.xml

Comment 2 The ASF infrastructure team 2022-09-24 20:38:15 UTC

This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4910