-
Notifications
You must be signed in to change notification settings - Fork 255
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
[jazzy] Performance improvements in Rosbag2 recorder discovery (backport #1825) #1827
Conversation
@ros-pull-request-builder retest this please |
Pulls: #1827 |
This is great that this is backported! Thank you! What is kind of the release rithm of rosbag2 jazzy? Would be good to know (kind of) when this would hit the binaries. |
@marcoag The last synch for Jazzy was Sep 6. When we would expect the next synch? |
There was a Jazzy patch release and sync on September 23: https://discourse.ros.org/t/new-packages-and-patch-release-for-jazzy-jalisco-2024/39727 |
Yeah, but the latest tag 0.26.5 for Jazzy in the Rosbag2 repo was created Sep.6 |
I was hoping to do one as soon as we get a fast-rtps and/or cyclone release, let's see how it goes in the next few weeks... |
But this |
@Timple yes, we usually do that on the week of the sync so we can catch the latest updates right before the sync happens. |
This PR improves the performance of the Rosbag2 recorder discovery by moving graph checks such as
topic_is_unpublished(topic_name, *node_graph_))
andis_leaf_topic(topic_name, *node_graph_))
, which are expensive to the end of the checklist.This PR is similar to the fix from 51a83f4 which was discussed in CPU overhead when discovery is used #1485. This gives a massive CPU improvement.
In the screenshot below you can see the performance difference:
This is an automatic backport of pull request #1825 done by [Mergify](https://mergify.com).