First knowledge of JMeter

1. JMeter Environment Preparation and operation
JMeter is an Apache-organized open source project and is a 100%-pure Java Desktop application for stress testing and performance testing
jmeter:http://jmeter.apache.org/download_jmeter.cgi
Installation Requirements:
1.1 Java version: On JVM1.5 or later (Java environment configuration does not say much here)
1.2 Operating system: can be run on any of the Java-deployed systems

1.3 JMeter After the download is complete, place a directory, unzip, just run the bin directory: Jmeter.bat (You can also set up a desktop shortcut) can run JMeter, run the interface as follows:

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/89/A9/wKiom1gZUpXS-DtQAADTS0cXNMo595.png "title=" Qq20161102103832.png "alt=" Wkiom1gzupxs-dtqaadts0cxnmo595.png "/>

2. JMeter Learning
2.1 Basic Concepts
1. Test plan: The starting point for testing using JMeter, which is a container for other jmeter test elements
2. Thread Group: Represents a certain number of concurrent users that can be used to impersonate a sending request from a concurrent user. The actual request content is defined in the sampler, which is contained by the thread group, can be set up in the test plan----Add a thread group, there are several input fields in the Thread Group panel: Number of threads, ramp-up Period (in seconds), number of loops, where Ramp-up Period (in seconds) indicates that all threads are created within this time. If there are 8 threads, ramp-up = 200 seconds, then the thread has a start interval of 200/8=25 seconds, and the benefit is that the server will not have too much load at first. Thread groups are designed to emulate concurrent workloads.
3. Sampler (Sampler): simulates various requests. All actual test tasks are performed by the sampler and there are many kinds of requests. such as: HTTP request
4. Listener: Responsible for collecting test results, but also be informed of the way the results are displayed. The function is to display the request results of the sampler, to statistic some data (throughput, kb/s ...). such as
5. Assert: Used to determine whether the result of the request response is correct as expected by the user. It can be used to isolate the problem domain, i.e. to perform a stress test if the function is correct.
6. Timer: Responsible for defining the delay interval between requests (threads), simulating successive requests to the server.
7. Logic controller: Allows custom jmeter to send request behavior logic, which is used in conjunction with sampler to simulate complex request sequences.
8. Configure the components to maintain sampler required configuration information, and modify the requested content according to the actual needs.
9. The predecessor processor and the post processor are responsible for completing the work before and after generating the request. The predecessor processor is often used to modify the requested settings, and the post processor is often used to process the response data.

3. About aggregate report (aggregated reports) parsing
Aggregate report is a listener commonly used in jmeter, and Chinese is translated into "aggregated reports".
If you are doing a performance test for a Web application, such as a single sign-on request, in aggregate report, a row of data is displayed, with a total of 10 fields, each with the following meanings.
Label: Each JMeter element (for example, HTTP Request) has a name attribute, which shows the value of the Name property

#Samples: Indicates how many requests you have made in this test, and if you simulate 10 users, each user iterates 10 times, then this shows a 100

Average: Average response time--the average response time of a single request by default, or the average response time in transaction when a transaction controller is used

Median: Median, which is the response time of 50% users

90% line:90% User's response time

Note: Meaning of the number of concurrent users 50% and 90%

Min: Minimum response time

Max: Maximum response time

error%: Number of requests with errors in this test/total number of requests

Throughput: Throughput--By default, indicates the number of requests completed per second (request per Second) when transaction is used

Controller, you can also indicate a loadrunner-like transaction per second number

Kb/sec: The amount of data received from the server side per second, equivalent to throughput/sec in LoadRunner

This article from the "Half wake half drunk half-floating" blog, please be sure to keep this source http://sweettexting.blog.51cto.com/12233355/1868371

First knowledge of JMeter