如果你想從頭學(xué)習(xí)Jmeter，可以看看這個(gè)系列的文章哦

前言

在 Jmeter 中一些專業(yè)名詞我們是需要提前認(rèn)知的，如下

Elapsed time

Latency

Connect Time

=======>>>> 點(diǎn)擊右側(cè)即可跳轉(zhuǎn)對應(yīng)詳解哦

Elapsed time

從發(fā)送請求到收到最后一個(gè)響應(yīng)，所花費(fèi)的時(shí)間

不包括渲染請求所花費(fèi)的時(shí)間，同時(shí)也不包括處理客戶端腳本所花費(fèi)的時(shí)間

JMeter measures the elapsed time from just before sending the request to just after the last response has been received. JMeter does not include the time needed to render the response, nor does JMeter process any client code, for example Javascript.

Latency

從發(fā)送請求到收到第一個(gè)響應(yīng)，所花費(fèi)的時(shí)間

該時(shí)間包括組裝請求、組裝響應(yīng)的第一部分所需的處理時(shí)間，通常長于一個(gè)字節(jié)

Jmeter 的時(shí)間應(yīng)該更接近瀏覽器或其他應(yīng)用程序客戶端所經(jīng)歷的時(shí)間

網(wǎng)上還有種說法，就是響應(yīng)信息越大，差別越大

JMeter measures the latency from just before sending the request to just after the first response has been received. Thus the time includes all the processing needed to assemble the request as well as assembling the first part of the response, which in general will be longer than one byte. Protocol analysers (such as Wireshark) measure the time when bytes are actually sent/received over the interface. The JMeter time should be closer to that which is experienced by a browser or other application client.

Connect Time

建立連接所花費(fèi)的時(shí)間

包括SSL三次握手的時(shí)間

注意：latency 沒有減去 connect time

當(dāng)出現(xiàn)鏈接超時(shí)等錯(cuò)誤，這個(gè)會(huì)等于鏈接超時(shí)時(shí)間

JMeter measures the time it took to establish the connection, including SSL handshake. Note that connect time is not automatically subtracted from?latency. In case of connection error, the metric will be equal to the time it took to face the error, for example in case of Timeout, it should be equal to connection timeout.

本文分享 CNBlog - 阿菠蘿阿瑤。

如有侵權(quán)，請聯(lián)系 support@oschina.cn 刪除。

本文參與“OSC源創(chuàng)計(jì)劃”，歡迎正在閱讀的你也加入，一起分享。

總結(jié)

以上是生活随笔為你收集整理的java中elapseTime设置新时间,Jmeter系列（44）- 详解 Elapsed time、Latency、Connect Time的含义...的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。