The Apache JMeter team released JMeter 3.1 on Nov. 20. The major release of JMeter 3.0 was in May, and we’re already seeing new features and improvements that improve your load testing and analysis abilities. CA BlazeMeter supports JMeter 3.1.
Which new abilities do you have in JMeter v. 3.1? Read this blog post to find out.
JMeter 3.1 is Here
Here are the 3 most important things you need to know about JMeter 3.1:
1. Open-Source Static HTML Report is Stronger
Reports and tables are crucial elements for analyzing test results. They can help you discover bottlenecks, learn about your system’s abilities and analyze trends and statistics.
JMeter 3.1 introduces new reports and summary tables.
Connect Time Over Time Graph
The Connect Time Over Time Graph enables users to view and analyze how long it took each request to connect, over the different times of the test. The Connection Time KPI is important for learning and understanding the responsiveness of the resource tested. Slow responsiveness leads to poor user experience and customer migration to competitors. Knowing when connection time was high can help determine its cause and help in fixing it faster. Display over time also shows trends.
Response Time Percentiles over Time (Successful Responses) Graph
This graph displays how long it takes the system to process successful requests, over time, for the different percentiles of the sample size. These are important for understanding your users’ experiences, while segmenting the user base. If you look at the 95th percentile, for example, you can determine the experience of the majority of users, while excluding extreme incidents. This is a better KPI for this purpose than Average. As you probably know, high response time over time leads to customer frustration which results in poor business and sales. As before, the analysis over time is crucial for detecting problems and identifying trends.
Response Time Overview Graph
This graph presents an overview of the time it took the system to process requests, for the complete test. Like the previous graphs, this display is also important for understanding the customer’s point of view of your site’s performance. If there were too many requests that had a higher response time than what you determined through your business criteria, you have a bottleneck you need to fix. The aggregation is helpful for quickly identifying system performance.
JMeter 3.1 will also present the top 5 errors in the Sampler summary table. This identification quickly points you to the issues that need fixing.
CA BlazeMeter also provides analysis, summary and trend reports, which you can read about here.
2. New ‘Sent Bytes’ KPI is Supported
Previously, JMeter only reported Received Bytes. In JMeter 3.1, Sent Bytes are also supported. This new feature provides users with information about how response time and connect time is influenced by the number of sent bytes. This enriches your analysis abilities.
3. Introducing Global Timer Scaling Factor Property
Pauses are an integral part of scenarios and test scripts. In real-life, customers might pause for 5 seconds after logging in, or pause for 10 seconds after conducting a search between items. These can be managed in load tests through JMeter timers.
However, if JMeter users want to update the test and change pause time configurations during script development, they need to manually change each timer. But not any more. In JMeter 3.1, the global timer enables users to update all pauses in one place. This is especially important in large scripts, and saves development time and meticulous work. Another way to save time is the step-by-step debugging feature CA BlazeMeter developed and released to open-source.
These changes in JMeter, along with memory improvements and a many performance improvements and optimizations, are a good reason to migrate to JMeter 3.1. CA BlazeMeter supports JMeter 3.1.
Learn more about JMeter
Click here to learn more about performance testing with JMeter, in this free webinar.
You might also find these useful:
Interested in writing for our Blog? Send us a pitch!