The speed test links at the bottom for single files don't make any sense. A single file download wouldn't benefit from the upgraded protocol and just seems, from very rough testing on my 100mb line, like the http/1 links are artificially slowed down.
HTTP/2 technology demo
71–80 of 100 posts
Re: HTTP/2 technology demo
#72It is interesting that Safari & Firefox beat Chrome in the HTTP/1.1 test for me. However, the HTTP2 test is then twice as fast as Safari. Maybe we can stop smashing all those javascript files together.
Re: HTTP/2 technology demo
#73Lol ran slower than http1 on my iPhone :/
Re: HTTP/2 technology demo
#74Earlier 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?
Yes, and if you do the Akamai test[0], which actually uses Keep-Alive, and enable pipelining in FF, it's possible to get HTTP/1.1 to within ~20-50% [1]. [0] https://http2.akamai.com [1] https://i.imgur.com/VJBKG36.png
I tried this test on mobile (iPhone 6 with iOS 9) over a flaky hotel wifi, and I got impressive results, 25s vs 3s: http://m.imgur.com/ND1wzZs
Also the OP test gave similar order of magnitude.
It looks like HTTP2 will be awesome for mobile!
Re: HTTP/2 technology demo
#75Perfect.
http://puu.sh/jIiG4/731c98e894.jpg
Re: HTTP/2 technology demo
#76Perfect. http://puu.sh/jIiG4/731c98e894.jpg
What browser?
Re: HTTP/2 technology demo
#77It 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.
Why not to fit your game into single HTML file, without any external dependencies?
Re: HTTP/2 technology demo
#78It 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…
This demo is representative of loading Clara.io scenes, lots of individual images and meshes: https://clara.io/view/b43f3215-c9ef-488f-a55f-1bf2a7d74f3f Yes, we could somehow package this up on the server and unpack it on the client, but I'd prefer HTTP/2 do that for us.
Took 40 seconds for it to load and the navigation to show up. Why is there no helpful message?
The loading bar is really small and doesn't provide enough feedback.
Re: HTTP/2 technology demo
#79Hm, HTTP/1.1 at 15.5s, HTTP/2 at 23.72s Yeah, I "can see the difference clearly", but I don't think it is the kind of difference they expected or intended. Edit: Firefox 40 on Windows 7 at work. Will try at home as well. Oddly enough, the Akamai demo someone else posted gives me 18.47s for HTTP/1.1 and 2.24s for HTTP/2.
At home (Firefox 40 on Windows 10) I get 2.34s for HTTP/1.1 and 1.26s for HTTP/2.
Re: HTTP/2 technology demo
#8012.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.
I don't think the limiting factor in "how much cruft should we add" is bandwidth. It's the point at which it becomes so hard to use that users leave.
Example: Buzzfeed loads in 1 second for me on my work's broadband, but it's still full of junk making it hard to use. Bandwidth-wise, it could handle more crap on the page, but in terms of usability it's at the limit.
I think you actually will get a faster and generally improved web when sites are finally able to end HTTP/1 support, because it will free up web developers from old performance hacks like asset concatenation, image sprites etc, which add a lot of friction to making websites.
All that said, this demo is bullshit for the reasons given in other comments.