discard DATAGRAM frames that don't fit into packets without an ACK #4221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4144. Closes #4145.
This PR implements part of my suggestion in #4145 (comment).
If the packet doesn't contain an ACK (i.e. the payload is empty), there's no point retrying to pack it later. It's extremely unlikely that the available packet size will suddenly increase.
Since we're relaxing the API guarantees (
SendDatagram
doesn't guarantee that the DATAGRAM frame is actually going to be sent out), this PR should allow us to move away from the blocking API (datagramQueue.AddAndWait
) that's the main cause for the bad datagram performance (#3766).@joliveirinha @chungthuang @birneee Could you take a look at this PR please? Does this resolve your problem?