Skip to content

Allow and track multiple publisher to same topic#55

Open
eliasdc wants to merge 10 commits intoirobot-ros:masterfrom
Tractonomy:multiple_publishers
Open

Allow and track multiple publisher to same topic#55
eliasdc wants to merge 10 commits intoirobot-ros:masterfrom
Tractonomy:multiple_publishers

Conversation

@eliasdc
Copy link
Copy Markdown
Contributor

@eliasdc eliasdc commented Aug 18, 2020

This PR adds the ability to have nodes publishing to the same topic to the benchmark application.

This adds a node_name attribute to the header message to keep track of the source of the message. A tracking number is saved for each unique node_name. This fixes an issue where the tracking_number_counter received the same number multiple times and the calculation of the stats failed because of it.

Size and frequency is saved in a Stat object to allow different sizes and frequencies with multiple publishers.

@eliasdc eliasdc requested a review from alsora as a code owner August 18, 2020 16:51
Copy link
Copy Markdown
Collaborator

@alsora alsora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution.
I like the new feature, but I have some doubts about the implementation.

Comment thread performances/performance_test/src/ros2/tracker.cpp Outdated
Comment thread performances/performance_test/src/ros2/tracker.cpp Outdated
Comment thread performances/performance_test_msgs/msg/PerformanceHeader.msg Outdated
@eliasdc eliasdc force-pushed the multiple_publishers branch from 16e570e to aaafd82 Compare August 25, 2020 17:41
@eliasdc eliasdc requested a review from alsora August 27, 2020 08:23
@alsora
Copy link
Copy Markdown
Collaborator

alsora commented Aug 27, 2020

@eliasdc I want to make sure that the application performance are not affected by the change, should be able to get results tomorrow.

@alsora
Copy link
Copy Markdown
Collaborator

alsora commented Aug 28, 2020

I compared your branch and master on a RaspberryPi 4 using the 20 nodes topology "montblanc".
master CPU usage is steady at 8.3%, while your branch CPU usage is steady at 11%.

I prefer to not merge the change as it is.
Next week will look more into the PR and see if we can optimize it somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants