Remove shared_mutexes to address concurrency performance #195
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.
Proposed changes
Removes the
shared_mutex
locks, that were not currently in use since there's no concurrency in how different steps of the filter are applied, but that was causing performance issues.Type of change
Checklist
Put an
x
in the boxes that apply. This is simply a reminder of what we will require before merging your code.Additional comments
Pre (before change) and post (after change) performance of the node.
Likelihood Sensor Model (linear scale)
Likelihood Sensor Model (log scale)
Beam Sensor Model (linear scale)
Beam Sensor Model (log scale)