Observed slower performance of HTTP/3 vs HTTP/2 in libcurl tests #21692
Unanswered
pkropachev
asked this question in
Q&A
Replies: 1 comment
-
|
My observations from 2 years ago: https://eissing.org/icing/posts/curl-h3-performance/ . There have been some curl improvement since, but HTTP/1.1 and HTTP/2 outperform on throughput still. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Team,
I performed a simple test to compare the performance of HTTP/2 and HTTP/3 using libcurl. The test measures the total time (CURLINFO_TOTAL_TIME_T) of requests for each protocol.
I used a locally running Caddy server on the same machine as the test client. The server serves a 10MB file, and the configuration is minimal:
I am using libcurl from the master branch:
The test code is straightforward: I perform 10 sequential requests (the connection is established during the first request and reused for subsequent requests). Each protocol test was run multiple times.
Observed results on my computer:
HTTP/2:
HTTP/3:
From these results, HTTP/3 appears slower than HTTP/2.
I also tried running the Caddy server on a separate machine over a real network, but the outcome was the same: HTTP/2 consistently outperformed HTTP/3.
I find this behavior surprising.
Has anyone observed similar performance characteristics with HTTP/3? Could there be something in my setup or test methodology that is causing HTTP/3 to underperform?
Beta Was this translation helpful? Give feedback.
All reactions