-
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
ndt7: save application level RTT samples #192
Comments
BTW, issue #201 seems to be a case where the RTT is actually 20-ish but BBR thinks it is much smaller, therefore, it would be beneficial to see what applevel-RTT says about the connection. |
I've done some shallow refactoring to include base The test produces expected difference between L7 and L4 RTT when TCP proxy is present on path. E.g. Tor Browser measures L7 / L4 RTT as It's also theoretically possible to modify What do you think, should it be |
@darkk considering how other speed tests work, I think may be preferable to include an application level |
* ndt7: measure and report L7 RTT based on websocket ping L7 ping may be significantly different from L4 pings and separate endpoint `/ping` is used to keep spec intact till further discussion happens. See 3520181 and #192 * ndt7: fix liveness bug in L7-RTT measurement Also, move that measurement data into to WSInfo sub-object as it's currently unclear if AppInfo should be extended or not. It's part of ndt7 spec :) TODO: squash this commit into previous one * Fix compatibility with go1.12 * ndt7: take one L7-RTT sample right before flooding the connection Co-authored-by: Simone Basso <bassosimone@gmail.com>
L7 ping may be significantly different from L4 pings and separate endpoint `/ping` is used to keep spec intact till further discussion happens. One L7-ping sent before `/download` test to get one sample that is not biased by the queue of bytes. L7 ping is logged as `WSInfo` sub-object as it's currently unclear if AppInfo should be extended or not. It's part of ndt7 spec :) See 3520181 and m-lab#192
L7 ping may be significantly different from L4 pings and separate endpoint `/ping` is used to keep spec intact till further discussion happens. See 3520181 and m-lab/ndt-server#192
* ndt7: measure and report L7 RTT based on websocket ping L7 ping may be significantly different from L4 pings and separate endpoint `/ping` is used to keep spec intact till further discussion happens. See 3520181 and m-lab/ndt-server#192 * ndt7: fix liveness bug in L7-RTT measurement Also, move that measurement data into to WSInfo sub-object as it's currently unclear if AppInfo should be extended or not. It's part of ndt7 spec :) TODO: squash this commit into previous one * Fix compatibility with go1.12 * ndt7: take one L7-RTT sample right before flooding the connection Co-authored-by: Simone Basso <bassosimone@gmail.com>
In #188, we have implemented the mechanism for measuring application-level pings RTT but we are not currently saving it. This should be done, to make the data actionable. We need to update the spec to mention this piece of data and change the code to save it.
The text was updated successfully, but these errors were encountered: