The benchmarks are not suitable to reach the conclusion that HTTP/3 is fast (or faster than HTTP/2). When you run such benchmarks, you choose a very fixed param

The benchmarks are not suitable to reach the conclusion that HTTP/3 is fast (or faster than HTTP/2). When you run such benchmarks, you choose a very fixed parameter vector (bandwidth, latency, link conditions that impact packet loss, payload shapes etc.). Running the same benchmark against a differently chosen parameter vector may result in the complete opposite conclusion. Additionally, the Internet is not a static system but a dynamic one. To say something is "fast", means that it should be fast for most people in most conditions. Sinle-link benchmarks are not feasible. I.e. in a traffic jam I will be very fast when I use the turn-out/emergency lane. But only as long as I am the only one doing it.