http2.0 Feasibility Study

First, HTTP2 has more new features than HTTP1.

1, the use of multiplexing technology, concurrent volume support than HTTP1 a few orders of magnitude;

2, binary sub-frame, improve network latency, improve transmission rate;

3, support header data compression, data volume smaller transmission faster;

4, support server push (single request multi-response);

Second, test comparison

Iii. Summary

It can be seen from the above test data that the http2.0 has the advantage when the number of concurrent requests (more than 30/s) and the network latency is large (greater than 30ms).

(This is the blog test and conclusion, I have not tested)

Combined with the characteristics of this project, use Nginx to do reverse proxy, provide to the business client and the web to obtain files; file servers, a day a service request volume of about 250W, Peak is three hundred or four hundred QPS, but most of the client sent requests, not supported HTTP2, a few browser requests, However, because there are more than one server, the basic is diverted, that is, the number of concurrent requests for a single service is very large;

Network latency is an unstable factor, does not prove that the server latency is large, may not be able to bring better returns, and the use of HTTPS speed will be slightly slower than HTTP (HTTP2 need to use HTTPS, the basic use of HTTP, the data has not yet required security);

Combined with the above analysis, the project status is not suitable for use HTTP2

Reference:

In-depth study: What exactly is HTTP2 's real performance?

What are the major improvements in http/2.0 compared to 1.0?

http2.0 Feasibility Study