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

Implement BBR holdback experiment to help diagnose unexpected ndt7 results #313

Open
mattmathis opened this issue Jul 27, 2020 · 4 comments
Labels

Comments

@mattmathis
Copy link

For some small fraction (1%?) of the ndt7 tests use CUBIC instead of BBR, to help identify the root causes of unexpected low performance.

@mattmathis
Copy link
Author

See also #314

@laiyi-ohlsen
Copy link

Good candidate for future OKR for long term data calibration and A/B testing

@mattmathis
Copy link
Author

I encountered another WiFi issue that might be due to an interaction with BBR. The only robust experiment to test this would be to see if CUBIC gets significantly better performance under similar scenarios.

@mattmathis
Copy link
Author

Tentative requirements (combining #351)

  • Enable the client to force CC from a list of valid names
  • If no forced CC from client, Use weighted random selection.
  • parameters for random selection should be set on then command line, such that they can be set in the container config.

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

No branches or pull requests

2 participants