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

Priority configuration for Publishers routes #81

Closed
JEnoch opened this issue Feb 9, 2024 · 0 comments · Fixed by #82
Closed

Priority configuration for Publishers routes #81

JEnoch opened this issue Feb 9, 2024 · 0 comments · Fixed by #82
Assignees
Labels
enhancement New feature or request

Comments

@JEnoch
Copy link
Member

JEnoch commented Feb 9, 2024

Describe the feature

In case of high traffic with big payloads and high CPU usage for a host, it may happen that some important messages with smaller payloads suffer an extra latency due to the fill of Zenoh transmission queue with big payloads waiting for fragmentation.
In such case, it would be good to have the important messages published on Zenoh with a higher priority. Thus Zenoh will make them overtake the big payloads in the queue, reducing the latency for higher priority messages.

Ideally the solution would be to map the DDS TRANSPORT_PRIORITY QoS to Zenoh Priority.
However, looking at ROS 2 rclpp interface, the TRANSPORT_PRIORITY is not exposed and cannot be set from ROS 2.

Therefore, the simplest solution is to add for the bridge configuration a setting allowing to configure the priority for the Publishers route, in a similar way than the pub_max_frequencies setting.

@JEnoch JEnoch added the enhancement New feature or request label Feb 9, 2024
@JEnoch JEnoch self-assigned this Feb 9, 2024
@JEnoch JEnoch closed this as completed in #82 Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant