On Fri, Jan 8, 2010 at 3:00 AM, Mike Belshe wrote:
Nice testing!
But for HTTP; the key seems to the pre-rendering-ready escape hatch in
> DocLoader::preload. Removing this gives me most all of the benefit. The
> comment says it pretty clearly: "Don't preload images or body resources
> before
.webkit.org] *On Behalf Of *Mike Belshe
> *Sent:* Thursday, January 07, 2010 3:09 PM
> *To:* webkit-dev@lists.webkit.org
> *Subject:* [webkit-dev] PreloadScanner aggressiveness
>
>
>
> Hi -
>
>
> I've been working on SPDY, but I think I may have found a good performa
On Thu, Jan 7, 2010 at 12:49 PM, Maciej Stachowiak wrote:
>
> On Jan 7, 2010, at 12:09 PM, Mike Belshe wrote:
>
> Hi -
>
> I've been working on SPDY, but I think I may have found a good performance
> win for HTTP. Specifically, if the PreloadScanner, which is responsible for
> scanning ahead wit
ists.webkit.org
[mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Mike Belshe
Sent: Thursday, January 07, 2010 3:09 PM
To: webkit-dev@lists.webkit.org
Subject: [webkit-dev] PreloadScanner aggressiveness
Hi -
I've been working on SPDY, but I think I may have found a good
perf
On Jan 7, 2010, at 12:09 PM, Mike Belshe wrote:
Hi -
I've been working on SPDY, but I think I may have found a good
performance win for HTTP. Specifically, if the PreloadScanner,
which is responsible for scanning ahead within an HTML document to
find subresources, is throttled today. T
Hi -
I've been working on SPDY, but I think I may have found a good performance
win for HTTP. Specifically, if the PreloadScanner, which is responsible for
scanning ahead within an HTML document to find subresources, is throttled
today. The throttling is intentional and probably sometimes necess
6 matches
Mail list logo
