You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we expose a number of (timing) statistics on a stream that is really useful for a sender side, but it doesn't help much for the receiver side:
It would be great if we could standardize a solution where the peer could give us its timing values too. This would allow a single side (i.e. the server) to get better understanding of where time is getting spent.
Proposed solution
Define a new QUIC extension to send peer timing statistics on shutdown of the send path of each stream.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like supported
Currently we expose a number of (timing) statistics on a stream that is really useful for a sender side, but it doesn't help much for the receiver side:
It would be great if we could standardize a solution where the peer could give us its timing values too. This would allow a single side (i.e. the server) to get better understanding of where time is getting spent.
Proposed solution
Define a new QUIC extension to send peer timing statistics on shutdown of the send path of each stream.
Additional context
No response
The text was updated successfully, but these errors were encountered: