Jmeter the listener and analysis of test results

Jmeter the listener and analysis of test results

Monitor

1 variety. . . Look interface

2, several commonly used:

Assertion results

Tree View Results

Aggregate Report

See the results in tabular

Graphical results

Aggregate graph

and many more. . . . . . . . . .

indicator anaysis

1, Samples: The scene completed a total of how many requests

2, Average: Average response time (average response time of the server process, with the server that the client requests information and the feedback processing time client)

3, Median: 50% median response time

4, 90% Line: 90% response time

5,

6、  Max

7, the above time in milliseconds. . . . Do not mistake

8, Error: error rate

9, Throughput: throughput, i.e. the number of requests per server process (server represents a client requests per second (units per second))

10, KB / sec: flow rate, the second server receives traffic data (represented by the server receives the client request indicates the number of KB per second)

11,% Processor time: cpu utilization rate (on average less than 75%, more preferably less than 50%)

Jtl file analysis - see test.jtl

1, in the performance testing process, we often need to test results stored in a file which, both to save the test results can also provide more material for future performance test report.

2, jmeter, the results are stored in .jtl file. This .jtl file can be written to provide a variety of formats, but in general we are to be recorded in CSV file format.

3, you only need to select a listener, configure a button click on the page, at this time, a setup interface will pop up, it is recommended checking the following items: Save Field Name, Save Assertion Failure Message

4, after the above settings, saved at this time .jtl file will have the following items:

TimeStamp,elapsed , label , responseCode , responseMessage , threadName , dataType,success,failureMessage,bytes,Latency

5, the request issued by the absolute time, response time, the request labels, return code, return information, the requesting thread belongs, data types, success, failure information, byte delay.

Guess you like

Origin www.cnblogs.com/yuany66/p/10974793.html