We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The ndt7 archival format does not include the average rate observed by the client or server. So, the data pipeline uses the last observed tcpinfo snapshot to calculate the average rates. https://github.com/m-lab/etl/blob/main/parser/ndt7_result.go#L165-L181
However, the ndt7 server does not guarantee when these snapshots are observed and recorded in the ServerMeasurements. This means that the archived last snapshot may not occur near the actual close of the connection. https://github.com/m-lab/ndt-server/blob/main/ndt7/download/sender/sender.go#L72-L86
ServerMeasurements
Ideally, when the server is shutting down the connection it would take and record one final snapshot.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The ndt7 archival format does not include the average rate observed by the client or server. So, the data pipeline uses the last observed tcpinfo snapshot to calculate the average rates. https://github.com/m-lab/etl/blob/main/parser/ndt7_result.go#L165-L181
However, the ndt7 server does not guarantee when these snapshots are observed and recorded in the
ServerMeasurements
. This means that the archived last snapshot may not occur near the actual close of the connection. https://github.com/m-lab/ndt-server/blob/main/ndt7/download/sender/sender.go#L72-L86Ideally, when the server is shutting down the connection it would take and record one final snapshot.
The text was updated successfully, but these errors were encountered: