HTTP/2 technology demo • Hacker News Board

Re: HTTP/2 technology demo

#41

Post by acdha » Thu, Aug 20, 2015, 2:30 PM UTC

takeda wrote: post #25

youngtaff wrote: post #14

It is a real world demo though? Similar to many of the other demo's of HTTP/2 (Gopher Tile, Akamai) it's written in a way that presents HTTP/1.x in the worst light and manages to screw things up even more. HTTP/1.1 is really latency prone so when you have a demo that uses lots of smalls requests that don't fill up the congestion window you run into a couple of problems. 1. The browser can only use a limited number of…

Regarding #4 isn't this a bit cheating, who doesn't use keep-alive. Also what about request pipelining? Doesn't that basically do the sane thing what http/2 is doing?

Others have pointed out why HTTP/2 is still better but if you're curious about HTTP pipelining here are the reasons why Firefox and Chrome disabled it after years of testing:

https://bugzilla.mozilla.org/show_bug.cgi?id=264354 https://www.chromium.org/developers/design-documents/network...

Re: HTTP/2 technology demo

#42

Post by JustSomeNobody » Thu, Aug 20, 2015, 2:31 PM UTC

jpmonette wrote: post #10

12.75s vs 1.40s. This is quite impressive - looking forward to a faster Web, slowly migrating to HTTP/2. Any clue if Amazon CDN service is / will offer HTTP/2 support too?

You won't get a faster web, you'll just get more cruft shoved on each page.

Re: HTTP/2 technology demo

#43

Post by patrickmcmanus » Thu, Aug 20, 2015, 2:33 PM UTC

youngtaff wrote: post #14

It is a real world demo though? Similar to many of the other demo's of HTTP/2 (Gopher Tile, Akamai) it's written in a way that presents HTTP/1.x in the worst light and manages to screw things up even more. HTTP/1.1 is really latency prone so when you have a demo that uses lots of smalls requests that don't fill up the congestion window you run into a couple of problems. 1. The browser can only use a limited number of…

good analysis.

worth mentioning that the h2 test actually respects the congestion window.. this helps both at the sending-too-slow stage, and also at the sending-too-fast stage which can easily be shown with h1 using parallel connections for large objects. (the parallelism essentially bypasses the congestion control at startup)

Re: HTTP/2 technology demo

#44

Post by mbq » Thu, Aug 20, 2015, 2:41 PM UTC

cflat wrote: post #9

This is a copy of the Akamai's http2 demo: http://http2.akamai.com

And Akamai's is inspired by http://http2.golang.org/gophertiles (which they acknowledge).

Re: HTTP/2 technology demo

#45

Post by james33 » Thu, Aug 20, 2015, 2:42 PM UTC

youngtaff wrote: post #14

It is a real world demo though? Similar to many of the other demo's of HTTP/2 (Gopher Tile, Akamai) it's written in a way that presents HTTP/1.x in the worst light and manages to screw things up even more. HTTP/1.1 is really latency prone so when you have a demo that uses lots of smalls requests that don't fill up the congestion window you run into a couple of problems. 1. The browser can only use a limited number of…

It may not be representative of the average page, but there are certainly ones that id does. When you load into our HTML5 game, you download over 1,000 PNG images on your first load. HTTP/2 is pretty exciting for us in that regard since we should see a significant improvement in load times.

Re: HTTP/2 technology demo

#46

Post by takeda » Thu, Aug 20, 2015, 2:42 PM UTC

noselasd wrote: post #37

takeda wrote: post #25

Earlier quoted context omitted.

Regarding #4 isn't this a bit cheating, who doesn't use keep-alive. Also what about request pipelining? Doesn't that basically do the sane thing what http/2 is doing?

Are there any browsers that have pipelining turned on by default ?