https://bz.apache.org/bugzilla/show_bug.cgi?id=65399
--- Comment #3 from Felix Schumacher <[email protected]> --- Thanks for the test plan. In my short tests, the first two times the GUI tests run faster, but the percentage of faster was nowhere near 100 or even 200 %. It was more 1 or 2 %. (I have done two tries, which is not really statistically relevant and a last test done after me writing this showed the non-GUI run faster 106 TX/s vs. 99 TX/s in the GUI) I even expanded the test duration (I used a duration of 100 seconds) and the GUI is (in that one run I did a bit) slower than running it without the GUI. (I have set up a local test server in order to avoid DOSing some random service) The results (from dashboard) were: GUI: 1204597 Requests total, 12051.15 TX/s, 97 max, 7 Median, 12 95%, 22 99% Non-GUI: 1235490 Requests total, 12358.61 TX/s, 83 max, 7 Median, 12 95%, 24 99% The reason for the (possibly true) advantage of the GUI for short test duration could be, that a JVM needs a bit to warm up and that we give it the time when loading a test plan and trying to find the right button to start it. In the non-GUI mode, that warm up phase is missing and it might hurt the performance of short tests (a wild guess). If you are wondering about differences between the stats when viewed in the dashboard, the aggregate report or excel, you might like to have a look at bug 65353. -- You are receiving this mail because: You are the assignee for the bug.
