-
Notifications
You must be signed in to change notification settings - Fork 5.5k
QUIC deferred logging: add retransmission rate #27699
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
Changes from 9 commits
34add06
c4476f9
606db28
bd39fb0
2f4f01a
4ce90b4
d7e673a
1c6fa73
a2b3a91
7f781be
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -580,6 +580,26 @@ class StreamInfo { | |
| */ | ||
| virtual uint64_t bytesReceived() const PURE; | ||
|
|
||
| /** | ||
| * @param bytes_retransmitted denotes number of bytes to add to total retransmitted bytes. | ||
| */ | ||
| virtual void addBytesRetransmitted(uint64_t bytes_retransmitted) PURE; | ||
|
|
||
| /** | ||
| * @return the number of body bytes retransmitted by the stream. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nothing else in here calls out it's body bytes. do we not track header bytes retransmitted? if not thoughts on naming?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Based on the relevant QUICHE code, I believe it indeed only tracks body bytes retransmitted. Do you mean we should rename the function to be specific about body bytes?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you're planning to implement this for HTTP/1 and 2 I assume they're going to track all bytes, in which case I'd be inclined to keep the naming the same and comment that for HTTP/3 it only tracks body bytes?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Agreed, sounds good.
This is still a totally open question. |
||
| */ | ||
| virtual uint64_t bytesRetransmitted() const PURE; | ||
|
|
||
| /** | ||
| * @param packets_retransmitted denotes number of packets to add to total retransmitted packets. | ||
| */ | ||
| virtual void addPacketsRetransmitted(uint64_t packets_retransmitted) PURE; | ||
|
|
||
| /** | ||
| * @return the number of packets retransmitted by the stream. | ||
| */ | ||
| virtual uint64_t packetsRetransmitted() const PURE; | ||
|
|
||
| /** | ||
| * @return the protocol of the request. | ||
| */ | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1160,6 +1160,7 @@ responder | |
| restarter | ||
| resync | ||
| ret | ||
| retransmissions | ||
| retransmitted | ||
| retransmitting | ||
| retriable | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you update logging docs to cover these as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!