Skip to content
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

deadline adoption for multi-fragment message #1510

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

yellowhatter
Copy link
Contributor

[closes #1494 ]

@yellowhatter yellowhatter added bug Something isn't working release Part of the next release internal Changes not included in the changelog labels Oct 4, 2024
@yellowhatter yellowhatter self-assigned this Oct 4, 2024
@yellowhatter yellowhatter marked this pull request as ready for review October 8, 2024 17:04
@yellowhatter
Copy link
Contributor Author

[closes #1494]

@yellowhatter
Copy link
Contributor Author

Briefly, improvements:

  • fix tests regression for multi-fragment message problem
  • fix perf regression for some platforms caused by too frequent time query
  • improve batching code readability (enum instead of cascaded options)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal Changes not included in the changelog release Part of the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

QoS: message fragments dropped
1 participant