Fix performance issue with contact data and AABB updates #1048
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.
🦟 Bug fix
Fixes #997
Summary
ComponentState::OneTimeChange
was used when updating theAxisAlignedBox
andContactSensorData
components which causes a full state serialization (all components serialized and sent over to state subscribers). In Fortress, we have some components that are expensive to serialize/deserialize, such ascomponents::ModelSdf
. However, we thought it was okay thinking they would be sent to the client once at the start of simulation. But withComponentState::OneTimeChange
, these components are serialized/deserialized repeatedly which causes a severe performance hit. UsingComponentState::PeriodicChange
instead makes it so that only the changed components are sent.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge