JMeter basic knowledge of performance testing (I.)

1. Download JMeter: Click here, download to complete the decompression can be

2. Start: Enter the extracted bin directory, Windows click Jmeter.bat, Linux execute JMeter

3. Add thread Group (user): Test Plan---add-Threads (Users)--thread group, here are Setup thread Group and teardown thread Gr OUP, the former is done before the test, the latter is done after the test. Here, click on test plan to have an execution plan setup is more commonly used, Run Thread Groups consecutively (I.e.one at time), tick to indicate sequential execution, refers to the existence of multiple thread groups in the test plans, The first thread group executes and then executes the next thread group. is the thread configuration details for the thread group:

4. Here are a few commonly used, some of the less common need to use the time, you go to try or find the information to see the document description.

Sampler: Commonly used HTTP request/ftp request/jdbc Request/java request, this is the core element, the specific test object is written here, the basic use of HTTP request, Post/get HTTP requests , here understand the HTTP protocol is a look, it is necessary to note that the encoding (sometimes garbled), Redirect automatically and follow Redirect difference, the former only for the get/head request, does not record the intermediate process, the latter is used to record the intermediate process .

Logic controller: Business logic Controllers, understand the programming of a look can understand this is what to do, the main commonly used are if/random and so on, random can also use Options-->function Helper dialog inside functions, such as : ${__random (1,100,num)}

Pre Processors: Pre-processor, executed before the sampler component, usually with the parameter setting (User Parameters), which is in detail when parameterized

Post processors: Post processor, executed after the sampler element, with more than regular Expression Extractor/xpath Extractor, here in connection with the time to elaborate

Assertion: Assertion, commonly used response assertion (there are many ways of comparison, according to the actual situation preferred choice)

Timer: Timer, generally used more is synchronizing timer, meeting point when used to

Config element: Configuration elements, which are different functions of the various components, such as HTTP request Defaults, the public request parameters are here in advance configuration, behind the specific sampler inside, the same part can be omitted to write

Listener: Listener, Common view results tree (view Results tree), Summary report (the difference between me and aggregation reports seems to be that there is a standard variance for response time), aggregated reports (Aggregate)

5. Final description of performance monitoring indicators

#Samples: Number of requests, number of samples

Average: Draw response time, Unit MS

Min: Minimum response time, Unit MS

Max: Maximum response time, Unit MS

Response time of the median:50% request

90%line:90% The response time of the request, the performance test is an important indicator

Response time of the 95%line:95% request

Response time of the 99%line:99% request

error%: Transaction error rate, typically no higher than 1%

Throughput: Throughput, the number of transactions completed per second, also known as TPS, is also an important indicator of performance testing, the larger the better, the greater the system's processing power

Received kb/sec: The amount of data received per second from the server side

Sent kb/sec: Amount of data sent to the server per second

Avg. Bytes: Average data traffic, in units of byte

Std.dev: Standard variance of response time

JMeter basic knowledge of performance testing (I.)