You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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?
The text was updated successfully, but these errors were encountered: