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

Performance benchmark updated results? #3

Open
pavan4 opened this issue May 9, 2017 · 5 comments
Open

Performance benchmark updated results? #3

pavan4 opened this issue May 9, 2017 · 5 comments

Comments

@pavan4
Copy link

pavan4 commented May 9, 2017

Thank you for the scripts and evaluation on QUIC.

Has this been run on the newest version of QUIC to compare the performance again with regards to TCP?

The wget links are 404's and there is a setup cost to run the benchmarking and hence I was wondering if there were any updates on the numbers available anywhere?

@pavan4
Copy link
Author

pavan4 commented Aug 7, 2017

I ran the performance benchmark and you can see the results here - > Updated Results

@bprodoehl
Copy link
Member

Nice!

@pavan4
Copy link
Author

pavan4 commented Aug 7, 2017

would be interesting to hear your thoughts when you have a chance to look at them?

@bprodoehl
Copy link
Member

My immediate thought was that we probably need to run each test about ten times before any true patterns emerge. There are some clear outlier results, where I'm guessing something just went wrong. Beyond that, I'm not sure if the trends where QUIC is faster and then HTTP gets faster will hold up. The loss scenarios, especially, can either be devastating to HTTP or no big deal at all, depending on where in the stream the loss occurs.

@pavan4
Copy link
Author

pavan4 commented Aug 22, 2017

Similar results were reported by others here

At low packet loss tcp is better, however as the packet loss is going up QUIC performs much better.

I expected FEC to improve this performance but apparently not. FEC has been disabled and there is discussion around 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