Return-Path: X-Original-To: apmail-jmeter-dev-archive@minotaur.apache.org Delivered-To: apmail-jmeter-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3BE510749 for ; Sun, 16 Nov 2014 13:33:22 +0000 (UTC) Received: (qmail 72722 invoked by uid 500); 16 Nov 2014 13:33:22 -0000 Delivered-To: apmail-jmeter-dev-archive@jmeter.apache.org Received: (qmail 72688 invoked by uid 500); 16 Nov 2014 13:33:22 -0000 Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jmeter.apache.org Delivered-To: mailing list dev@jmeter.apache.org Received: (qmail 72676 invoked by uid 99); 16 Nov 2014 13:33:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Nov 2014 13:33:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of philippe.mouawad@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Nov 2014 13:32:56 +0000 Received: by mail-ie0-f180.google.com with SMTP id rp18so373496iec.25 for ; Sun, 16 Nov 2014 05:32:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=9BTWFOELs+Zaoz1leZ0hCv/IH65+uqaWVaadkCzKBFc=; b=npV+kaiYOIw1mBacljM0knijIcWmd+1RMYHkSNCXz569f5BNVzI4gWkVHNjxnLMtiW 2Q9kEGbhAauX94uWIH2roWZMbfU5FcAIVm63j0XnKl6z5k6wQB0NZg0c0ObPv9MqCgX+ 6wA9Dbi3FTolsPMQhRoQ2yD0DwNf6/t+n1Yfhx7dVqHz4gPwkfIXBq/bOtLmhKA/43MT 2mXkUZPM9LdLXcX05U4lJedM0fEZL8wuEjRbo8TKTJ+TMidkpLOnn/EX1OknECU+qyID 1NQHI8ILwiOVyWG5Qv6g9wkUUSVR2oralDuMSfUBTVUjpio8JbFawWoquxelqOf2xt1r GV4Q== MIME-Version: 1.0 X-Received: by 10.50.111.8 with SMTP id ie8mr19256696igb.37.1416144775771; Sun, 16 Nov 2014 05:32:55 -0800 (PST) Received: by 10.42.102.131 with HTTP; Sun, 16 Nov 2014 05:32:55 -0800 (PST) Date: Sun, 16 Nov 2014 14:32:55 +0100 Message-ID: Subject: Graphs and reporting in Apache JMeter : Today and Future From: Philippe Mouawad To: "dev@jmeter.apache.org" Content-Type: multipart/alternative; boundary=089e0149c0284f7cce0507f9e697 X-Virus-Checked: Checked by ClamAV on apache.org --089e0149c0284f7cce0507f9e697 Content-Type: text/plain; charset=ISO-8859-1 Hello, I would like to start a discussion about the future of graphs and reporting in Apache JMeter. Todays state: - My feeling (I don't want to hurt anybody who worked on those listeners which are interesting and I am aware that what can be great at some time can become less few years after) is that today: - we have the following graphs - Aggregate Graph : currently affected by bug on https://issues.apache.org/bugzilla/show_bug.cgi?id=57221 in Java 8 - Response Time Graph : interesting but slow to generate and I get OOM when I try to reload an existing CSV in some configuration, I will report a bug - Distribution Graph (alpha) : Alpha is not encouraging for users, is Alpha really needed or is it stable - Graph Results : Does not look very nice compared with what you can get today - we have the following reports: - Aggregate Report : Interesting - Summary Report: Differs from Aggregate Report by having additional Avg Bytes and Std Dev but not Median nor 90%Line My opinion and analysis on the current state is the following: - We lack of clean reporting that would be generated automatically at end of load test, all the previous graphs need to be generated from GUI and makes you lose some time. Also as we discourage Load Testing from GUI we should propose a way to generate reporting from NON GUI Mode - Some graphs (Response Time Graph, Aggregate Graph) rely on JCharts which seems to be abandoned, last release is from 2004 and current bug 57221 may be related to a bug in the library ,by the way this is an additional argument to get rid of obsolete libraries in JMeter: - Avalon (Logging + DataSource) - Excalibur (logging + DataSource) - jCharts - Reports are not sufficient and partly redundant , for example it seems that in terms of information Aggregate report and Summary Report should be merged. I looked at their code they are really very similar , I think one should be removed and the infos in both merged I must reckon that today my colleagues and I for example , we all use JMeter-Plugins graphs combined with GraphGeneratorListener, and we are very happy with what we get: - http://www.ubik-ingenierie.com/blog/automatically-generating-nice-graphs-at-end-of-your-load-test-with-apache-jmeter-and-jmeter-plugins/ I would be interested to know how users generate their reports and graphs currently. But some may object that JMeter-Plugins is not JMeter and conclude that JMeter lacks of an essential feature. So I have 2 propositions to improve JMeter in this field: - 1/ Create a Brand new Report Generator Listener that would at end of load test generate a report in HTML or PDF containing: - Merge of informations contained in current reports - Generate graphs based on JS Libraries, I am impressed by the number of libraries that generate nice and sexy graphs: - http://www.chartjs.org/ - https://github.com/keen/dashboards/tree/gh-pages/examples - Having them in HTML would allow some dynamice behaviour but the ideal result would be to be able to export graphs also as images - 2/ I don't know if it is possible but what about merging JMeter-Plugins graphing suite + GraphGeneratorListener in JMeter core if no library is in conflict in terms of licensing, of course it would required their agreement :-) I think today any Load Testing tool comes with reporting feature wether Commercial and Open Source and JMeter as such should improve in this field to stay one of the leaders in Load Testing field. Thoughts ? -- Regards Philippe M. @philmdot --089e0149c0284f7cce0507f9e697--