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

Squash participants #160

Open
Gronfi opened this issue Nov 12, 2020 · 1 comment
Open

Squash participants #160

Gronfi opened this issue Nov 12, 2020 · 1 comment

Comments

@Gronfi
Copy link

Gronfi commented Nov 12, 2020

Hi,
what are the practical implications of activating this option in the ospl.xml file?
on the other hand, is there any aspect that stops working the same? is there more consumption of resources like memory or cpu?
Is there perhaps less network traffic due to DDS at discovery time and generally in normal operation?

@vivekpandey02
Copy link

Hi Gronfi,

When Squash participant is enabled then ddsi will advertise only one participant to the outside world. Thus all application participants will not be visible by the other nodes. Thus this will save discovery overhead (less memory use and somewhat less network traffic) . The disadvantage is that the liveliness of individual participants can not be monitored.
Especially when dds security is used this could make a lot difference because you do not have to authenticate each participant.

With best regards,
Vivek Pandey
Solutions Architect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants