Jmeter插件解释

时间:2019-06-17
本文章向大家介绍Jmeter插件解释,主要包括Jmeter插件解释使用实例、应用技巧、基本知识点总结和需要注意事项,具有一定的参考价值,需要的朋友可以参考一下。

Jmeter插件解释

1、jp@gc - Actiive Threads Over Time:不同时间活动用户数量展示(图表) 
2、jp@gc - AutoStop Listener :自动停止监听器 
average Response Time is greater than 10000ms for 10 seconds :连续10s平均响应时间大于10000ms就停止测试。 
average Latency is greater than 5000ms for 10 seconds :连接10s平均等待时间大于5000ms就停止测试。 
Error Rate is greater than 50% for 10 seconds :10s内错误率一直高于50%就停止测试。 
3、jp@gc - Bytes Throughput Over Time:不同时间吞吐量展示(图表)(聚合报告里,Throughput是按请求个数来展示的,比如说1.9/sec,就是每s发送1.9个请求; 而这里的展示是按字节Bytes来展示的图表) 
4、jp@gc - Composite Graph: 混合图表 
在它的Graphs里面可以设置多少个图表一起展示,它可以同时展示多个图表 
5、jp@gc - Console Status Logger:一些log的设置。 
这是一个简单的侦听器将简短的摘要日志打印到控制台,JMeter是在非gui模式下运行。它还写jmeter相同的信息。登录GUI模式。

注意,响应时间和平均延迟值打印出来。

 

6、jp@gc - Flexible File Writer:这个插件允许你灵活记录测试结果 
Filename:结果记录的地方 
Overwirte existing file:是否覆盖这个文件 
Write File Header:文件的头(即文件的第一行) 
Record each sample:如何记录不同的sample(记录哪些内容,用什么顺序,如何隔开不同的值) 
Write File Footer:文件的结尾(即文件的最后一行) 
startTime epoch time when request was started 

开始时间:时代的时候请求开始
endTime epoch time when reading response ended 

结束时间:时代的时候阅读反应结束
responseTime response time, time to full response loaded 

响应时间:响应时间,时间完全响应
latency latency, time to first response byte received (if available) 

延迟:延迟时间的第一反应字节收到(如果可用)
responseCode response code (200, 404 etc.) 

对应:《(200404等等)
responseMessage response message (OK, Not Found etc.) 

响应消息:响应消息(好吧,不是发现等等)
responseHeaders response headers (if present in sample) 

响应头:响应头在样本(如果存在)
responseData response data 

响应数据:响应数据
requestData request data from sample 

请求数据请求的数据样本
sentBytes number of request bytes sent, if available 

发送字节:发送请求的字节数,如果可用
receivedBytes number of request bytes sent (if available) 

收到的字节:发送请求的字节数(如果可用)
threadName name of thread in Thread Group that processed request 

商标名的名字:处理请求的线程在线程组
sampleLabel name of the sampler that made request 

样品取样器:使请求的标签名称
isSuccsessful is response was marked as successful 

Succsessful反应是标记为成功
isFailed is response was marked as failed (surrogate field) 

是失败的反应:是标记为失败(替代字段)
startTimeMillis same as startTime, but divided by 1000 (surrogate field, example: 1311121131.362) 

开始时间,米尔斯一样开始时间,但是除以1000(代理领域,例如:1311121131.362)
endTimeMillis same as endTime, but divided by 1000 (surrogate field) 

结束时间,结束时间,米尔斯一样但除以1000(替代字段)
responseTimeMicros same as responseTime, but multiplied by 1000 (surrogate field) response Time Micros same as response Time, but multiplied by 1000 (surrogate field) 
latencyMicros same as latency, but multiplied by 1000 (surrogate field) 

延迟微指令一样延迟,但乘以1000(替代字段)
variable# Sample variable with index N, see below for details

变量#样本变量指数N,详情见下文

7、jp@gc - Hits per Second:每秒点击量 
8、jp@gc - Loadosophia.org Uploader:This is special plugin in for uploading results to Loadosophia.org immediately after test end. 

这是特殊的插件上传结果测试结束后立即到Loadosophia.org


9、jp@gc - Page Data Extractor:以图表的形式展示页面上你想得到的一些结果,它以正则表达式的形式获取key和vale。(下面的key和value的正则表达式以括号标志) 
10、jp@gc - PerfMon Metrics Collector:服务器性能监测控件,包括cpu,memory,network I/O等等。(JMeter cannot retrieve by default server metrics except Tomcat ones.:就是jmeter只能监控tomcat的主机)(前提是要先在服务器上startAgent,即把插件解压到服务器上,运行startAgent) 
11、jp@gc - Reponse Codes per Second:This graph will display the response code per second returned during the test. 

这个图表将显示在测试期间每秒响应代码返回。
12、jp@gc - Reponse Latencies Over Time:This graph will display the response latencies during the load test. A latency is the duration between the end of the request and the beginning of the server response.(就是记录客户端发送请求完成后,服务器端返回请求之前这段时间) 
13、jp@gc - Reponse Times Distribution:This graph will display the response time distribution of the test. The X axis shows the response times grouped by interval, and the Y axis the number of samples which are contained in each interval. 

他的图将显示的响应时间分布测试。X轴显示了响应时间按间隔分组,Y轴的样品数量是包含在每一个时间间隔。


14:jp@gc - Respose Times Over Time:This graph will display for each sampler the average response time in milliseconds. 

这个图表将显示为每个采样器的平均响应时间,以毫秒为单位。
15、jp@gc - Response Times Percentiles:This graph will display the percentiles for the response time values. X Axis represents percentage, Y Axis Response time values. One point (P, Value) means for the whole scenario, P percent of the values are bellow Value ms.(没太明白) 

这个图表将显示响应时间值的百分位数。X轴代表比例,Y轴响应时间值。一个点(P)意味着对于整个场景,P值的百分比女士咆哮的价值。


16:jp@gc - Response Times vs Threads:This graph shows how Response Time changes with amount of parallel threads. Naturally, server takes longer to respond when a lot of users requests it simultaneously. This graph visualizes such dependencies. 

这个图表显示了响应时间变化与并行线程的数量。当然,服务器响应时间变长很多用户同时请求它。这张图可视化这些依赖关系。


17:jp@gc - Transaction Throughput vs Threads:This listenter is very similar to Response Times vs Threads, exept it shows total server’s transaction throughput for active test threads. listenter非常类似于响应时间和线程,使用它显示总服务器的事务吞吐量测试的活动线程。
18、jp@gc - Transactions per Second:This graph shows the number of transactions per second for each sampler. It counts for each seconds the number of finished transactions.这个图表显示的数量为每个取样器每秒事务数。计数为每个秒完成交易的数量。

原文地址:https://www.cnblogs.com/jane4321/p/11042521.html