| Summary: | Improve Response Time Graph Y axis scale with huge values or small values (< 1000ms). Add a new field to define increment scale. | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Luca <luca.maragnani> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 2.9 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Attachments: | Patch to RespTimeGraphChart.java | ||
Thanks for your patch. I will work on a global patch to accept a high increment scale for the high values, and a very little increment for scale with the little responses times (<1000ms). I think add in GUI response time graph a new field "Increment scale" for personalize the increment. done. URL: http://svn.apache.org/r1444399 Log: Improve Response Time Graph Y axis scale with huge values or small values (< 1000ms). Add a new field to define increment scale Bugzilla Id: 54532 Modified: jmeter/trunk/docs/images/screenshots/response_time_graph.png jmeter/trunk/docs/images/screenshots/response_time_graph_settings.png jmeter/trunk/src/components/org/apache/jmeter/visualizers/RespTimeGraphChart.java jmeter/trunk/src/components/org/apache/jmeter/visualizers/RespTimeGraphVisualizer.java jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jmeter/trunk/src/core/org/apache/jmeter/resources/messages_fr.properties jmeter/trunk/xdocs/changes.xml jmeter/trunk/xdocs/images/screenshots/response_time_graph.png jmeter/trunk/xdocs/images/screenshots/response_time_graph_settings.png jmeter/trunk/xdocs/usermanual/component_reference.xml This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3055 |
Created attachment 29927 [details] Patch to RespTimeGraphChart.java The Y axis scale is not readable when there are samples with high response times because scale step is 500ms. IMHO scale should be adjusted considering graph size and max response time. In attach a simple patch to address the problem: the hypothesis is that a single item needs 50px to be readble.