Config: tune some values for ROS 2 use cases (backport #509) #515
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.
ROS 2 systems can experience a large number of nodes (e.g. >200) starting all together.
This may lead to having a large number of connections be initialised at the same time during the startup phase.
This PR updates some Zenoh default limits that are deemed too small for the ROS 2 cases for both the Router and the Nodes. The reason for each update is documented directly in the config files.
No behaviour change is expected to be introduced by this PR, just a smoother out-of-the-box experience for large use cases.
This is an automatic backport of pull request #509 done by Mergify.