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

Document best practice on setting QoS settings for topics #583

Open
azeey opened this issue Jul 30, 2024 · 1 comment
Open

Document best practice on setting QoS settings for topics #583

azeey opened this issue Jul 30, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@azeey
Copy link
Contributor

azeey commented Jul 30, 2024

As mentioned in #581, for example, the clock topic should use the ClockQoS setting. It would be nice if we had a list of recommended QoS settings for different types of topics.

@azeey azeey added the enhancement New feature or request label Jul 30, 2024
@azeey azeey changed the title Document Document best practice on setting QoS settings for topics Jul 30, 2024
@azeey azeey moved this from Inbox to To do in Core development Jul 31, 2024
@Kametor
Copy link

Kametor commented Dec 13, 2024

Hi, I encountered a similar issue when using ros_gz_bridge with a high-bandwidth camera topic and a pose topic. When both are bridged together in the same instance, I experienced significant lag in pose updates.

Following the recommendation in Issue #581, running the camera topic in a separate ros_gz_bridge instance solved the problem. This workaround took me hours to figure out, so it might be worth addressing this with a better fix, like default QoS settings or improved multithreading support 😊

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: To do
Development

No branches or pull requests

2 participants