hack: Prioritise UDP disco messages #3237
Draft
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.
Description
This should help with disco messages being dropped because the AsyncUdpSocket is hogging the socket's internal lock because it being asked to send so much data.
The unbounded queue is essentially bounded by the concurrency of the writers to the socket, so will stay small.
Breaking Changes
Notes & open questions
The code duplication, the unbounded queue (which is bounded really).... It's a quick hack right now. Though I'm not sure how nice it can be made right now.
Change checklist
quic-rpc
iroh-gossip
iroh-blobs
dumbpipe
sendme