本文介绍了spdy比keep-alive https更快?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我见过和,但。

我甚至注意到了根据我自己的经验,两者都只比ping几分钟。

I've even noticed that both are just a few ms more than ping in my own experience.

我错过了什么?我用这个来安装。有没有我错过的设置?

Am I missing something? I used this to install http://www.howtoforge.com/using-mod_spdy-with-apache2-on-ubuntu-12.10. Is there a setting I missed?

推荐答案

这个问题太模糊了,无法有效回答。 SPDY通过单个连接提供基于帧的多路复用。帧可以对应于HTTP请求头,或HTTP请求主体块,或HTTP响应头,或HTTP响应主体块。如果你只使用一个请求/响应,那么SPDY将提供最小的优势(如果你认为CPU很便宜,那么有一些,可能是最小的延迟优势,因为报头压缩会牺牲CPU时间和线路上的字节的内存,这是序列化延迟的主要输入。)

This question is far too vague to be able to be effectively answered. SPDY provides frame-based multiplexing over a single connection. A frame may correspond to HTTP request headers, or HTTP request body chunks, or HTTP response headers, or HTTP response body chunks. If you only use one request/response, then SPDY will provide minimal advantage (there's some, probably minimal, latency advantage if you assume CPU is cheap, since the header compression will trade off CPU time and memory for bytes on the wire, which is the primary input into serialization latency).

这篇关于spdy比keep-alive https更快?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-03 20:56
查看更多