The obtained number will give us the average amount of users visiting our web page in any given time. We can calculate the number of users per second with the formula: Then we must calculate the number of users per second, which we’ll directly input into our JMeter Thread Group configuration. – Average time a visitor spends on the site: Tu (in seconds) – Average number of visited pages per visit: Na Google Analytics stores the following pieces of information for us: We can turn to the site statistics, like Google Analytics and write down the average number of users, or better yet, the maximum number of users visiting our web page at any given time. Normally we can do a better job than guessing a number of users that we expect to be visiting a web page at a time. In the previous parts of the JMeter tutorials we talked about measuring the best throughput with the specified average number of users we expect to be visiting the website at any given time.

Testing the Performance of InfoSec Institute We must look for the maximum throughput, which we observed in the third use case, but we must also have a constant throughput, which we observed in the fourth use case, which implies that the best ramp-up period is somewhere in between 10 and 100 seconds.Ģ. In the above cases the best ramp-up period was somewhere in between 10 and 100 seconds. This means that when we’re sending all requests close together, the server can still process them fairly quickly, but not as fast as when we’re introducing a slight delay between the requests, which is logical. We can notice that the number of requests is increasing with the bigger ramp-up period up until some point (til fourth case). The first case has a throughput of 429.098 requests/minute, the second case has a throughput of 416.437 requests/minute, the third case has a throughput of 1015.916 requests/minute, the fourth case has a throughput of 597.699 requests/minute and the last case has a throughput of 60.022 requests/minute. This further implies that we should lower the ramp-up period to increase the load on the server. A constant throughput with a low requests/minute value means that we’ve set the ramp-up period too high, because the target application (server) can process the previous requests before the next request is even sent. If we take a look at the throughput we can see that in the first three cases it’s rising considerably, but in the last two it is constant. The picture below contains the results of performance testing with a Ramp-Up period of 1000 seconds (therefore 1 request will be sent per second): The picture below contains the results of performance testing with a Ramp-Up period of 100 seconds: The picture below contains the results of performance testing with a Ramp-Up period of 10 seconds: The picture below contains the results of performance testing with a Ramp-Up period of 2 seconds: The picture below contains the results of performance testing with a Ramp-Up period of 0 seconds (therefore all requests are sent at once): In this section we’ll present various results we received with the JMeter when testing the performance of the web site.įirst, let’s change the Ramp-up period to 0, 2, 10, 100, 1000 seconds and observe the results when simulating 1000 users and repeating the loop only once. There is no need to configure the Graph Result element, so we didn’t provide a picture. We also added the graph result listener that can show us the results of the test plan. In the HTTP Request element we specified that we want to access a resource /index.html as can be seen in the picture below:

We specified only the “Server Name or IP” to be b) HTTP Request We used three elements, that we won’t describe in detail, since they have already been described in other parts of this tutorial series. Let’s present the options that we used when running the test cases in this tutorial. We can do that by simply pressing the Menu – Run – Start button. When everything is set-up all that is left for us to do is run the JMeter and observe the results.

Apache jmeter 4 download