Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Cuts Chrome Page Load Times In Half w/ SPDY

Posted by CmdrTaco on from the well-that-seems-optimistic dept.

An anonymous reader writes "It appears as if Google has quietly implemented the SPDY HTTP replacements in Chrome (well, we knew that), and its websites. All its websites were recently updated with SPDY features that address some of the HTTP latency issues. The result? Google says the pageload times were cut about in half. SPDY will be open source, so there is some hope that other browser manufacturers will add SPDY as well."

3 of 310 comments (clear)

  1. Detailed info on SPDY by NevarMore · · Score: 5, Informative

    http://www.chromium.org/spdy/spdy-whitepaper

  2. SPDY clarifications by mbelshe · · Score: 5, Informative

    Thanks for all the kind words on SPDY; I wish the magazine authors would ask before putting their own results in the titles!

    Regarding standards, we're still experimenting (sorry that protocol changes take so long!). You can't build a new protocol without measuring, and we're doing just that - measuring very carefully.

    Note that we aren't ignoring the standards bodies. We have presented this information to the IETF, and we got a lot of great feedback during the process. When the protocol is ready for a RFC, we'll submit one - but it's not ready yet.

    Here are the IETF presentations on SPDY:
          http://www.ietf.org/proceedings/80/slides/tsvarea-0.pdf
    and
          https://www.tools.ietf.org/agenda/80/slides/httpbis-7.pdf

    I've also answered a few similar questions to this here: http://hackerne.ws/item?id=2420201

    We love help- if you're passionate about protocols and want to lend implementation help, please hop onto spdy-dev@google.com Several independent implementations have already cropped up and the feedback continues to be really great.

  3. Re:BAD by mbelshe · · Score: 5, Informative

    Actually, you should read the spec as to how it is implemented. The TLS/NPN mechanism for switching to SPDY has no "fallback".

    And there is no intent to rush - heck - we've been working on it for over a year. You think that's rushed? If you're an engineer, I hope you'll appreciate that protocol changes are hard. You can't use pure lab data (although we started out with lab data, of course). Now we need real world data to really figure it out. We changed it in a way which *nobody noticed* for about 4 months. So, I don't think we hurt the web at all, but we are accomplishing the goals of learning how to build a better protocol.

    Seriously, if you have a better way to figure out new protocols, we'd love to hear them at spdy-dev@google.com, and if you want to lend a hand implementing, that is even better!