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.

Sign up for GitHub

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

Jump to bottom

TCPinfo schema in prod behind sandbox #107

Open
mattmathis opened this issue Nov 9, 2021 · 2 comments
Open

TCPinfo schema in prod behind sandbox #107

mattmathis opened this issue Nov 9, 2021 · 2 comments
Labels
review/triage Team should review and assign priority

Comments

@mattmathis
Copy link
Contributor

Something was not deployed.

The last 4 fields of sandbox.ndt.ndt7:Download.ServerMeasurements.TCPinfo
are ReordSeen, ElapsedTime, RcvOOOPack and SndWnd. The TCPinfo schema in prod all end with either ReordSeen or ElapsedTime. (ndt.ndt7, ndt.tcpinfo).

Unfortunately the SndWnd is the most important field for understanding client bottlenecks.

ElapsedTime, which is locally generated (and not part of the native TCPinfo structure) should have been first.
@autolabel autolabel bot added the review/triage Team should review and assign priority label Nov 9, 2021
@stephen-soltesz
Copy link
Contributor

Investigating over VC, the underlying tables include the SndWnd field. The view may be stale. However, recent measurements do not appear to have the SndWnd field populated. This may be a failure of collection or parsing. TBD.

@stephen-soltesz
Copy link
Contributor

Spot checking a random archive from 2021/11/08 I see SndWnd in the JSON files. So, I would imagine there is a disconnect between the parser and BQ.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
review/triage Team should review and assign priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stephen-soltesz @mattmathis