Improve contact sensor / visualization performance #1452
Merged
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.
Signed-off-by: Ian Chen [email protected]
🦟 Bug fix
Summary
This PR improves contact sensor performance by using a new
GetByPhysicsId
function inEntityFeatureMap
for faster retrieval of gazebo entities from physics ID.The original call uses the
Get
function that requires casting toShapePtrType
which causes a big performance hit when done many times in a for loop. The cast is needed because the two types are actually different.With this change, I noticed that for our application with ~70 contact points, the computation time of the for loop for building the contact map drops from 2.x ms to 0.02x ms. This gives us ~10% RTF Improvement with a contact sensor in the world.
You can manually test this with shapes.world:
Visualize Contacts
GUI PluginBefore this change, the RTF on my machine is roughly 3x%. After this change, it hovers around 8x%
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.