RE: Performance implications of Bundling and Minification on HTTP/1.1

Karl,

Indeed, the data here is from cold-start.

It would be nice to check various forms of caching as well but up front I would observe that bundling and minification again would likely help you as you only have to manage 2 cached resources and not N resources that may all have to get validated individually. Bundled/Minified content are just bigger documents.

Also, having the links way at the top of the HTML will also help as you would get to the links faster and as a result be able to start validating them with the cache faster.

Henrik

-----Original Message-----
From: Karl Dubost [mailto:karld@opera.com] 
Sent: Friday, June 22, 2012 1:55 PM
To: Henrik Frystyk Nielsen
Cc: HTTP Working Group; Howard Dierking
Subject: Re: Performance implications of Bundling and Minification on HTTP/1.1

Henrik,

Le 22 juin 2012 à 13:18, Henrik Frystyk Nielsen a écrit :
> We just published a blog [1] analyzing the performance implications of content optimizations such as bundling and minification on the performance of web pages.

Very nice !

> leverage optimizations throughout the stack to provide better user experience.

All the tests and benchmarks we see (even if made on real Web sites) are what I call "cold start testing". Basically every is set to 0, we download everything and look at the protocol design impacts on performances. 

But when we talk about better *user* experience, we might want to take into account the impact on performances when the user is doing multiple actions on the same set of resources. HTTP caching enters into play.

Is the performance gain that big? Are there things which can be done in the protocol to take into account longterm usage scenario?



-- 
Karl Dubost - http://dev.opera.com/
Developer Relations, Opera Software

Received on Friday, 22 June 2012 21:05:36 UTC