I actually measured how much performance is different between HTTP / 2 and HTTP / 3 - Latest to understand visually: Nikkei Cross Tech Active
There is no day when we do not use a web browser on our PCs or smartphones. In addition to reading various articles, it is now possible to do many things on the web that can be done with apps installed on the OS, such as email, music and videos, SNS, shopping, chat and video conferencing, and document creation. In this special issue, we will explain the latest technologies of the Web.
This time, we will introduce the interesting features of QUIC and the performance measurement results of HTTP/3.
An interesting feature of QUIC is "0-RTT" using TLS 1.3. RTT (Round Trip Time) is the time it takes to make a round trip. Before HTTP/3, even if a server had been connected once before, when sending a request again, it was necessary to perform multiple exchanges such as TCP connection and TLS negotiation between the client and server.
On the other hand, as the name 0-RTT suggests, TLS-encrypted HTTP requests are sent over UDP. If it is a server that has communicated once, the session can be resumed at once using the pre-shared key that was generated.
"0-RTT", an advantage of QUIC [Click image to enlarge]Let's check how this 0-RTT is actually used using Google Chrome and Wireshark.
I used Google Chrome 92.0 here. Start Google Chrome and open the top page of Google. Next, if you reload the web browser or open Google's top page in another tab, you can actually check the 0-RTT packet with Wireshark.
As you can see, HTTP/3 and QUIC have many interesting features.
Check 0-RTT with Chrome developer tools and Wireshark [Click image to view larger image]Nikkei Crosstech Active selects products and services for companies in the IT, manufacturing, and construction fields. This is an information site that supports the introduction of We post a lot of content such as product / service information and introduction examples. Please register as a member (free) when viewing for the first time.