tag:blogger.com,1999:blog-581197352358126527.post715139076328730133..comments2024-03-29T03:21:30.339-07:00Comments on japh(r) by Chris Strom: SPDY/3 Flow Control ComparisonsAnonymoushttp://www.blogger.com/profile/00135361916531185929noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-581197352358126527.post-45174657984550414022012-05-24T07:32:42.982-07:002012-05-24T07:32:42.982-07:00To be fair to chrome, you have an absurdly high bd...To be fair to chrome, you have an absurdly high bdp path there because of the ~infinite bandwdith of localhost combined with the injected delay. That is going to exaggerate the effect.<br /><br />otoh these kinds of idle round trips you're seeing to fix the window are exactly the kind of phenomenon spdy/2 eliminated through parallelism that make it work so well. So there is irony in spdy/3 introducing new ones:)<br /><br />you will eventually see firefox make use of flow control in conjunction with server push and probably eventually with media streams. it certainly has niche uses on the client side and I'm glad to see it be part of the protocol - I think you're just seeing how easy it is to configure it in ways that slow things down in unexpected places. It needs some tweaking as a protocol element to make it more robust.Patrick McManushttps://www.blogger.com/profile/00565702107491976279noreply@blogger.com