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

[22604] Filter interested readers on PDP writer (backport #5604) #5657

Open
wants to merge 1 commit into
base: 3.1.x
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 21, 2025

Description

This fixes a high CPU and network usage situation with PDP simple discovery when a new participant is created in a network where there is a high number of existing participants.

@Mergifyio backport 3.1.x 3.0.x
An ABI compatible backport would be manually done to 2.14.x, and we will backport to other 2.x supported branches from there.

Contributor Checklist

  • Commit messages follow the project guidelines.

  • The code follows the style guidelines of this project.

  • Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally

  • Any new/modified methods have been properly documented using Doxygen.

  • N/A: Any new configuration API has an equivalent XML API (with the corresponding XSD extension)

  • Changes are backport compatible: they do NOT break ABI nor change library core behavior.

  • Changes are API compatible.

  • N/A: New feature has been added to the versions.md file (if applicable).

  • N/A: New feature has been documented/Current behavior is correctly described in the documentation.

  • Applicable backports have been included in the description.

Reviewer Checklist

  • The PR has a milestone assigned.
  • The title and description correctly express the PR's purpose.
  • Check contributor checklist is correct.
  • If this is a critical bug fix, backports to the critical-only supported branches have been requested.
  • Check CI results: changes do not issue any warning.
  • Check CI results: failing tests are unrelated with the changes.

This is an automatic backport of pull request #5604 done by [Mergify](https://mergify.com).

* Refs #22506. Regression test.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Add `PDPStatelessWriter` extending `StatelessWriter`

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Use `PDPStatelessWriter` in `SimplePDPEndpoints`

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Move specific API to `PDPStatelessWriter`.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Initial work on management of interested writers.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Take advantage of single sample history.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Reset state after sending datagram.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Filter interested readers.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Do not reset unsent changes upon participant discovery.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Fix AsymmeticIgnoreParticipantFlags test.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22506. Create sender resources for matched readers.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22708. Rename methods.

Signed-off-by: Miguel Company <[email protected]>

* Refs #22708. Avoid allocations using a `ResourceLimitedVector` instead of an `std::set`

Signed-off-by: Miguel Company <[email protected]>

* Refs #22604. Improve monitor service blackbox tests.

Reducing announcement period to improve discovery timing.

Signed-off-by: Miguel Company <[email protected]>

---------

Signed-off-by: Miguel Company <[email protected]>
(cherry picked from commit 8eb1072)
@MiguelCompany MiguelCompany self-requested a review February 21, 2025 09:17
@MiguelCompany MiguelCompany added this to the v3.1.3 milestone Feb 21, 2025
@github-actions github-actions bot added the ci-pending PR which CI is running label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-pending PR which CI is running
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant