Conversation
Merge master back to develop after vere-v4.5
Inbound peek packets are capped relative to the outstanding scry requests for the whole pier; inbound pokes are capped relative to the ovum queue of the mesa driver (which also includes page responses to our own outbound requests). Both caps are low to avoid "buffer bloat".
The 408 pre-release has encountered all kinds of problems and a constant among them has been that mesa sending 10 packets every two minutes on broken flows behaves significantly worse than old ames sending just one. There have been multiple mitigations for "stuck" flows recently but having any that exist be 10x worse than before is unacceptable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.