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

I did an experiment and the result is http1.1 better than http2... #4226

Closed
Kyson opened this issue Aug 22, 2018 · 3 comments
Closed

I did an experiment and the result is http1.1 better than http2... #4226

Kyson opened this issue Aug 22, 2018 · 3 comments

Comments

@Kyson
Copy link

Kyson commented Aug 22, 2018

Hi,

I did an experiment:

  1. Download “Network Link Conditioner” for mac. In this software, choose network to "Very bad" which is 10% loss package and 500ms delay.
  2. Android Device connect mac's wifi.
  3. In my app code:

image

enable http2 then send 100 same requests, and it fail 20+ times

  1. disable http2 then send 100 same requests, and it fail about 5 times

This result is no accident, because i tried for many times.

Before I thought http2 is better than http1.1 ,especially when network is bad. But the truth is not.

So why is this happening? Is there some bug with okhttp's http2?

Thank u very much.

@swankjesse
Copy link
Member

Related: https://www.twilio.com/blog/2017/10/http2-issues.html

@Kyson
Copy link
Author

Kyson commented Aug 30, 2018

@swankjesse Thank you very much , i will read this post.

@yschimke
Copy link
Collaborator

The takeaway here could be to make concurrency of a single stream tunable or controllable. Also maybe applies to sharing Video and critical API calls over the same connection, especially with coalescing.

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

3 participants