Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP3 faster than HTTPS1.1 or HTTP 2 for blob download.. reasons? #84

Closed
hoax-killer opened this issue Oct 13, 2019 · 4 comments
Closed

Comments

@hoax-killer
Copy link

hoax-killer commented Oct 13, 2019

Hi,
I have used your platform to do large blob downloads (e.g. 1G) files and force the browser to not exceed more than 1 parallel connection for download.

I see that HTTP 3 is much faster than HTTP 2 and 1.1.
For instance,
HTTPS 1.1 took 55 seconds
HTTP 2 took 50 seconds
HTTP 3 took 35 seconds.

Can anyone explain:

  • Why HTTP 2 is faster than HTTP 1.1?
  • Why is HTTP 3 faster than HTTP 1.1 and HTTP 2?

I know the overheads, but such high difference is what I am not sure.

Any thoughts?

Arvind

@dtikhonov
Copy link
Contributor

Which server was serving HTTP/1.1 and HTTP/2 -- LiteSpeed Web Server or something else? As for HTTP/3, did you use LSWS as well?

lsquic uses BBR by default, so that may explain the difference in throughput. Try changing it to Cubic to see how well it does.

@hoax-killer
Copy link
Author

I used OpenLiteSpeed to see perf. across all versions 1.1, 2 and 3.

I read about the BBR, I plan to get some results with cubic today. Sure, BBR is aggressive.
But why would HTTP 2 be faster than 1.1?
I am not sure if overheads will have that much of an impact.

@dtikhonov
Copy link
Contributor

The HTTP/1.1 vs HTTP/2 question is better asked in openlitespeed.

@hoax-killer
Copy link
Author

hoax-killer commented Oct 15, 2019

Sure, if I get an answer or meaningful thoughts, will post it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants