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

That sounds fantastic!  I'd be happy to put it into ID form or the blog  -- might have to redo the graphics ;)

As for more data in high-latency environments -- I completely agree -- it's on the list and I hope to provide some data next week. I would also like to see data through proxies.

Btw, I hope to make the data/source available soon so that people can try it out as well.

Henrik

-----Original Message-----
From: Mark Nottingham [mailto:mnot@mnot.net] 
Sent: Friday, June 22, 2012 18:21
To: Henrik Frystyk Nielsen
Cc: HTTP Working Group; Howard Dierking
Subject: Re: Performance implications of Bundling and Minification on HTTP/1.1

Hi Henrik,

Thanks very much for doing this. 

I'd like to see much more data like this; without it, it's too easy to make decisions based upon popularity and momentum rather than reasoned goals, especially when engineers clamour for Shiny New Things. Mike and the Google guys have done some fantastic work in this area, but we need multiple sources and repeatable tests.

It'd be nice to see this in a more permanent form; e.g., as an I-D, or copied to the WG wiki. Blog entries have a habit of disappearing. (Mike et al, if you'd like to copy your data over as well, please get in touch; we could start a bit of a repository there).

Also, I'd *really* like to see more data about higher-latency connections. Personally, the majority of Web sites I use on a daily basis have a ping time in excess of 200ms, and that's going to be the experience of many across the globe (not just those in .au and .nz).

Cheers,



On 23/06/2012, at 3:18 AM, Henrik Frystyk Nielsen wrote:

> We just published a blog [1] analyzing the performance implications of content optimizations such as bundling and minification on the performance of web pages. The data shows that by applying bundling and minification along with compression and pipelining it is possible to get significant gains in the time it takes to get the content necessary to render a page as well as the overall time it takes to download the data.
>  
> Not only does optimizing the content save bytes but it also has savings in the number of requests and responses that need to be processed as well as faster render times due to being able to retrieve the HTML, CSS, and JS up front. In the test evaluated, the speedup was from 638 ms (uncompressed, unbundled, unminified, and not pipelined) down to 146 ms for the equivalent compressed, bundled, minified, and pipelined content. However, by just looking at the data necessary to lay out the page (HTML, CSS, and JS but not images), the time went from 631 ms to 126 ms with the images being finalized within the remaining timespan from 126 to 146 ms.
>  
> It is the hope that this data can contribute to providing a baseline for evaluating HTTP/2.0 proposals compared to how an efficient HTTP/1.x implementation can perform while leverage optimizations throughout the stack to provide better user experience.
>  
> Comments welcome!
>  
> Thanks,
>  
> Henrik
>  
> [1] http://blogs.msdn.com/b/henrikn/archive/2012/06/17/performance-implications-of-bundling-and-minification-on-http.aspx

--
Mark Nottingham   http://www.mnot.net/

Received on Saturday, 23 June 2012 01:30:06 UTC