Tomcat series of performance tests -Jmeter

A. Preparations

1. Jdk1.8 installed and configured environment variable.
   
2. In Apache's official website to download the latest Jmeter. Jmeter official website
   
3. Tomcat8 mainstream, we measured the pressure Tomcat8 performance.

II. Application start

Here we do not need to build any project, you can start Tomcat, Tomcat itself comes with the application.

Start default port is: 8080, start mode: bio-threaded blocking mode.

Three .Jmeter performance test

1. Open Jmeter, select the Test Plan, click the Edit menu button, select the Add operation, select Thread (Users), and then select the Thread Group to create a thread group.
   
2. Select the Thread Group, click the Edit menu button, select the Add operation, select Sampler, and select Http Request. I measured pressure is their new applications, as:
   the results shown in Figure:
   Http request configuration as shown:
   
3. Select the Test Group, click on the Edit menu Anqiu, select the Add operation, select Listener, then add the Aggregate Graph (Aggregate Report), View Results Tree (see the results of the tree), respectively.
   
4. Start Tomcat, the default port 8080.
   
5. Click the green button to execute the plan.
   
6. View polymerization report.
   

Detailed reporting parameters polymerizable four .Jmeter

1. Label: JMeter of each element (e.g. HTTP Request) has a Name property, label is displayed in the Name attribute.
2. #Samples: this test that you have issued a total number of requests, as I opened the 150 threads, each cycle 10 times, so my total was 1500.
3. Average: Average response time - the default is the average response time of a single Request, the Controller Transaction when used, may be displayed in units of Transaction Average response time.
4. Median: the median response time is 50% of users.
5. 90% Line: 90% response time for users.
6. Min: minimum response time.
7. Max: maximum response time.
8. Error%: requested number of errors occurring in this test / total number of requests.
9. Throughput: certain default represents the case where the number of completed requests per second (Request per Second), when using a Transaction Controller, can be expressed per Second Transaction number of similar LoadRunner.
10. KB / Sec: second server receives the amount of data, equivalent to the LoadRunner Throughput / Sec.

V. Conclusion

As shown, it can be seen such a simple configuration, Tomcat throughput of 1472 / sec, process 1472 requests per second. Of course, this is only in the local case, if released to the line, but also consider network latency, data size, server CPU, memory and so on. So it should analyze the specific measure pressure situation.

So far, Jmeter pressure measurement Tomcat8 performance, end the test.

Resources:
Use JMeter to stress-test Tomcat and Tomcat Performance Tuning