支出是将数据/要求上载到服务器的时间。 这发生在封锁和等待之间。 例如,如果我重新贴出伙伴关系司的网页,这将表明把申请(包括表格的数值和届会状态)上传回伙伴关系服务器所需时间。

放弃是请求发出后的时间,但在收到服务器的答复之前。 基本上,这是等待服务器回复的时间。

接收时间是从服务器下载回复的时间。

Blocking是国际不动产业联合会启动申请和吉大港不动产业协会要求进入电线之间的时间。

这些顺序如下:

1. Blocking*
2. DNS Lookup
3. Connecting
4. Sending
5. Waiting
6. Receiving

*Blocking and DNS Lookup might be swapped.

表格没有显示处理时间。

如果你有很长的阻挡时间,则管理浏览器的机器运行缓慢。 你们可以通过提升机器(更长的援助团、更快的加工商等)或减少其工作量(放弃不需要的服务、关闭方案等)来解决这一问题。

Long wait times indicate that your server is taking a long time to respond to requests. This either means:

• The request takes a long time to process (like if you are pulling a large amount of data from the database, large amounts of data need to be sorted, or a file has to be found on an HDD which needs to spin up).
• Your server is receiving too many requests to handle all requests in a reasonable amount of time (it might take .02 seconds to process a request, but when you have 1000 requests there will be a noticeable delay).

The two issues (long waiting + long blocking) are related. If you can reduce the workload on the server by caching, adding new server, and reducing the work required for active pages then you should see improvements in both areas.

https://developers.google.com/chrome-developer-tools/docs/network#about_the_resource_timing_api” 官方解释。 这是一种真正有益的资源,你的信息载于timeline view节。

Resource network timing shows the same information as in resource bar in timeline view. Answering your quesiton:

• DNS lookup: Time spent performing the DNS lookup. (you need to find out IP address of site.com and this takes time)
• Blocking: Time the request spent waiting for an already established connection to become available for re-use. As was said in another answer it does not depend on your server - this is client s problem.
• Connecting: Time it took to establish a connection, including TCP handshakes/retries, DNS lookup, and time connecting to a proxy or negotiating a secure-socket layer (SSL). Depends on network congestion.
• Sending - Time spent sending the request. Depends on the size of sent data (which is mostly small because your request is almost always a few bytes except if you submit a big image or huge amount of text), network congestion, proximity of client to server
• Waiting - Time spent waiting for the initial response. This is mostly the time of your server to process and respond to your response. This is how fast if your server calculating things, fetching records from database and so on.
• Receiving - Time spent receiving the response data. Something similar to the sending, but now you are getting your data from the server (response size is mostly bigger than request). So it also depends on the size, connection quality and so on.

Blocking: Time the request spent waiting for an already established connection to become available for re-use. As was said in another answer it does not depend on your server - this is client s problem.

我不同意上述发言。 所有其他都是相同的[我的机器工作量]——我的浏览器显示一个网站的“锁定”时间要小得多,有些其他网站的封隔时间很长。

因此,如果等待六条之环+代理谈判** 中的一条,主要是因为服务器慢慢慢或页码设计不好[多半通过电线发送]。

** - whatever "Proxy Negotiation" means!, nobody explains this very well, particularly where no local/CDN proxy is actually involved