微服务环境中的平均响应时间和平均周转时间有什么区别?
ISO 说明:
平均响应时间:
How long is the mean time taken by the system to respond to a user task or system task?
平均周转时间
What is the mean time taken for completion of a job or asynchronous process?
我目前正在通过计算响应延迟时间的平均值来测量平均响应时间。差异是否可能是在测量平均响应时间时仅发送 1 个(同步)请求,并且在测量平均周转时间时可能使用多个线程并使用多个请求访问服务?
或者平均响应时间只是衡量系统需要响应的时间,而响应本身并不重要?
两个时间的测量结果(在微服务环境中)有何不同?我不使用任何异步响应。
区别可能是
MRT = 延迟, MTT = 耗时?
Elapsed time. 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. 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.
最佳答案
据我所知,响应时间是系统对收到的请求生成响应所需的时间。它是从系统收到请愿书到发出响应的那一刻开始计算的。
另一方面,周转时间是完成请愿所需的时间。它是从发送请愿书的那一刻到收到答复的那一刻进行衡量的。
MRT和MTT只是多个请愿书中针对这些时间的相应手段。
使用客户端-服务器示例:
PS: Petition Sent
PR: Petition Received
RS: Response Sent
RR: Response Received
[client] [ network ] [ server ] [ network ] [client]
PS ---------------- PR ------------ RS ------------------- RR
0 ms 730 ms 940 ms 1620 ms
\ \________________/ /
\ response time /
\______________________________________________________/
turnaround time
响应时间为 940 - 730 = 210 毫秒,即服务器生成响应所需的时间。
周转时间为1620毫秒,即客户端收到响应所需的时间。
JMeter 的“耗时”与此处的周转时间相同,而“延迟”则是客户端开始接收响应所需的时间。如果响应是通过 1000 Mbps 线路传输的 10 MB 数据 block ,则完全接收大约需要 80 毫秒,因此消耗的时间将为延迟 + 80。
关于microservices - 平均响应时间与平均周转时间 (DIN_IEC_25023) 差异?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/53944603/