-
Notifications
You must be signed in to change notification settings - Fork 42
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
Explore pacing-gain to understand early termination #315
Comments
https://console.cloud.google.com/bigquery?sq=581276032543:5a15dedd9d1a4133b498357ddc54929f Looks like pacing gain usually drops below 1.25 within less than 5 seconds. Need more analysis. |
WRONG - bug in SQL
92% converge within 1 second |
Of those that converge: |
The average convergence time is about 1.4 seconds, and average BytesAcked at convergence is about 69MB. |
Found another SQL bug. The spreadsheet has been updated. The worst 5%, with convergence time > 4.8 seconds, average 28 MBytes (log mean 4MB), and the latest converging average around 40 to 60 MBytes. The BBRInfo.MinRTT averages around 1 msec (log mean 0.88) for the fastest converging tests, and around 200 msec for tests that take 6 seconds or more to converge. On average, it looks like it takes around 25 to 30 minRTT to converge, but sometimes as few as 5 or 10, and sometimes 1000s of MinRTTs. |
Median number of round trips to convergence is around 25 for fastest convergence, up to 50 for the slowest convergence. |
I've refined the query to actually look for first two crossings, from <=1 to <1, and from <1 to >=1. This changes the results slightly, but not dramatically. |
BQ connected spreadsheet comparing throughput, BBR_BW at convergence, and BBR_BW at 10 sec. |
Needs design discussion with @pboothe |
We have a lot of ndt7 data now, and should explore the pacing-gain behavior, to understand how well early termination could work based on pacing-gain, and also verify whether there is an earlier fixed termination time that would be effective for 95+ percent of clients.
The text was updated successfully, but these errors were encountered: