了解Chrome网络日志“已停用”州 [英] Understanding Chrome network log "Stalled" state
问题描述
我有一个以下网络日志chrome：
我不明白其中的一点：填充灰色条和透明灰色条之间有什么区别。 b
Google在评估网络性能部分的DevTools文档。
摘自资源网络计时：
$ b
失速/阻止
请求等待发送之前等待的时间。这一次包括花在代理商谈判上的时间。此外，这段时间将包括浏览器何时等待已建立的连接可用于重新使用，请遵循Chrome的
基本上，你会看到这一点的主要原因是因为Chrome只会下载6每次服务器的文件一次和其他请求将被阻止，直到连接插槽变为可用。
这不一定是需要修复的东西，而是一种避免的方法停滞状态将是分布在多个域名和/或服务器上的文件，保持 CORS ，但HTTP2很可能今后一个更好的选择。资源绑定（如JS和CSS连接）也可以帮助减少停滞连接的数量。
I've a following network log in chrome:
I don't understand one thing in it: what's the difference between filled gray bars and transparent gray bars.
解决方案 Google gives a breakdown of these fields in the Evaluating network performance section of their DevTools documentation.
Excerpt from Resource network timing:
Stalled/Blocking
Time the request spent waiting before it could be sent. This time is inclusive of any time spent in proxy negotiation. Additionally, this time will include when the browser is waiting for an already established connection to become available for re-use, obeying Chrome's maximum six TCP connection per origin rule.
(If you forget, Chrome has an "Explanation" link in the hover tooltip and under the "Timing" panel.)
Basically, the primary reason you will see this is because Chrome will only download 6 files per-server at a time and other requests will be stalled until a connection slot becomes available.
This isn't necessarily something that needs fixing, but one way to avoid the stalled state would be to distribute the files across multiple domain names and/or servers, keeping CORS in mind if applicable to your needs, however HTTP2 is probably a better option going forward. Resource bundling (like JS and CSS concatenation) can also help to reduce amount of stalled connections.
这篇关于了解Chrome网络日志“已停用”州的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
失速/阻止
请求等待发送之前等待的时间。这一次包括花在代理商谈判上的时间。此外，这段时间将包括浏览器何时等待已建立的连接可用于重新使用，请遵循Chrome的 基本上，你会看到这一点的主要原因是因为Chrome只会下载6每次服务器的文件一次和其他请求将被阻止，直到连接插槽变为可用。 这不一定是需要修复的东西，而是一种避免的方法停滞状态将是分布在多个域名和/或服务器上的文件，保持 CORS ，但HTTP2很可能今后一个更好的选择。资源绑定（如JS和CSS连接）也可以帮助减少停滞连接的数量。 I've a following network log in chrome: I don't understand one thing in it: what's the difference between filled gray bars and transparent gray bars. Google gives a breakdown of these fields in the Evaluating network performance section of their DevTools documentation.
Excerpt from Resource network timing:
Stalled/Blocking
Time the request spent waiting before it could be sent. This time is inclusive of any time spent in proxy negotiation. Additionally, this time will include when the browser is waiting for an already established connection to become available for re-use, obeying Chrome's maximum six TCP connection per origin rule.
(If you forget, Chrome has an "Explanation" link in the hover tooltip and under the "Timing" panel.)
Basically, the primary reason you will see this is because Chrome will only download 6 files per-server at a time and other requests will be stalled until a connection slot becomes available.
This isn't necessarily something that needs fixing, but one way to avoid the stalled state would be to distribute the files across multiple domain names and/or servers, keeping CORS in mind if applicable to your needs, however HTTP2 is probably a better option going forward. Resource bundling (like JS and CSS concatenation) can also help to reduce amount of stalled connections.
这篇关于了解Chrome网络日志“已停用”州的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
