Use getTopicTypes() in /rosapi/get_topics for increased performance #381
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.
Hello,
When using
rosapi
in the development of web applications for the PR2 robot, I was facing the problem that the call for the/rosapi/topics
service was extremely slow (operating with over 1200 topics).Looking into the problem, it seems that getting the types was taking a lot of time:
By using the
Master.getTopicTypes()
we can get equivalent results (the order changes) with better performance:Note that differently from
Master.getSystemState()
,Master.getTopicTypes()
also includes inactive topics and does not include topics with unknown messages.Related to: ros/ros_comm#53