ChromeDriver - 网络性能日志记录：了解 Network.responseReceived 的计时部分

Question

我正在尝试了解网络性能日志消息的计时部分中属性之间的关系。

设置：我是运行带有网络性能日志记录的 ChromeDriver。我正在提取日志消息 (Selenium - Java)。以下是示例日志消息和我目前的理解。

message => params => response => timing
{
    "requestTime": 126550.470936,          : Time in sec when the browser knows the call has to be issued?
    "proxyStart": 1.77299999631941,        : Is this a relative time in ms from requestTime? What this latency accounts for?
    "proxyEnd": 3.25700000394136,          : Time taken to resolve the proxy in ms?
    "dnsStart": -1,                        :  
    "dnsEnd": -1,                          : Time taken to resolve the dns?
    "connectStart": -1,                    :
    "connectEnd": -1,                      : Time taken to establish the connection with remote server? 
    "sslStart": -1,                        :
    "sslEnd": -1,                            : Is this part of "connect" section? (time taken to negotiate SSL handshake?)
    "workerStart": -1                      :
    "workerReady": -1,                     : 
    "sendStart": 582.229000006919,         : 
    "sendEnd": 582.65900000697,            : Time taken to send the request to server?
  "pushEnd": 0,                          :
    "pushStart": 0,                        : Unclear as what this accounts for.
    "receiveHeadersEnd": 1218.61900000658  : Time taken to completely receive the header?
}

我试图从上面的时间划分中理解以下部分。

浏览器发出请求所用的时间（典型的排队延迟在网络选项卡中可见）。
浏览器建立连接和发送请求所用的时间
服务器处理请求所用的时间
收到回复所用的时间。

任何关于此的指示都会很棒。

Answer 1

这些是我的理解

延迟是receiveHeadersEnd。

代理时间是proxyEnd - proxyStart.

发送时间为sendEnd - sendStart.

等待时间是receiveHeadersEnd - sendEnd.

请参考： https://groups.google.com/forum/#!topic/google-chrome-developer-tools/cuIpVMC1C4U

Answer 2

我从另一组得到答案https://groups.google.com/forum/#!topic/google-chrome-developer-tools/FCCV2J7BaIY

ChromeDriver - 网络性能日志记录：了解 Network.responseReceived 的计时部分

ChromeDriver - Network Performance Logging: Understanding timing section of Network.responseReceived

performance

logging

selenium-chromedriver

timing