浏览器并发线程 [英] Browser concurrent threads

问题描述

我一直在四处寻找的线程模型信息/数常见的浏览器使用。

I've been looking around for information on the threading model / count common browsers use.

具体来说，我可以想象，当浏览器访问一个页面，将揭开序幕，新的线程下载链接的资源（CSS /图片等），它需要渲染页面。我假设有一个有限的限制，并发线程，他们将使用，这将节省带宽资源接近页面的顶部，这样的倍以上的东西会很快呈现量。

Specifically I imagine when a browser visits a page it will kick off new threads to download the linked resources (css / images etc.) it needs to render the page. I assume there is a finite limit to the amount of concurrent threads they will use, this would conserve bandwidth for the resources nearer the top of the page so the "above the fold" stuff will render quickly.

没有任何一个有关于他线程在特定的现代浏览器使用的池大小的信息吗？另外，如果我的简单化操作请让我知道。

Does any one have any information on the size of he thread pools used in specific modern browsers? Also if I've oversimplified their operation please let me know.

推荐答案

异步下载不需要单独的线程;它们是由操作系统来处理

Asynchronous downloads do not require separate threads; they're handled by the operating system.

然而，浏览器都具有一个上限数目的连接到每个域名（通常为2，6,8，或15）。 （火狐）的（IE ）

However, browsers do have an upper bound (usually 2, 6, 8, or 15) on the number connections to each domain name. (Firefox) (IE)

这篇关于浏览器并发线程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！