[tor-dev] Proposal: Optimistic Data for Tor: Client Side
ksbauer at gmail.com
Sat Jun 4 21:58:43 UTC 2011
> Assuming you mean "stream" instead of "circuit" here, then, as above, I
> think most HTTP connections would be in this category. It might be
> interesting to examine some HTTP traces to see, though. <shoutout
> target="Kevin">Kevin, you were looking at some HTTP traces for other
> reasons, right? Anything in there that may help answer this
This is a great question.
Google released a study about a year ago  that characterized crawled web pages in terms of their total size, the number of distinct destination hosts per page, the number of HTTP GETs per page, and other attributes. Their data indicates that the median web page requires that the client connect to 5 distinct destination hosts and issue 6.25 GETs per host.
Put another way, a typical web page requires 5 streams, each of which issue multiple GETs. The full distributions of these statistics are available at .
Assuming persistent HTTP connections, with this proposal, only a stream's initial GET request would experience an improvement in time-to-first-byte, while subsequent GETs would be unaffected.
However, by reducing the time-to-first-byte for even just the first request per stream, the user is able to start fetching subsequent streams sooner, and thus, retrieve the whole page faster.
More information about the tor-dev