vehicle: improve performance by removing has_part( "ROTOR" ) calls #44941
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.
Summary
SUMMARY: Performance "vehicle: improve performance by removing has_part( "ROTOR" ) calls"
Purpose of change
has_part( "ROTOR" )
checks every part in a vehicle to see if the part is a rotor. This is ridiculously expensive in compute time and unnecessary, because the presence of rotors is cached invehicle::rotors
which is automatically refreshed invehicle::refresh()
.Profiling was showing that 6% of overall compute time was spent
has_rotor( "ROTOR" )
calls.Describe the solution
Replace the calls to
( has_part( "ROTOR" ) && has_part( "ROTOR_SIMPLE" ) )
with!rotors.empty()
for a noticeable performance boost.Describe alternatives you've considered
More caching could be done in
vehicle::check_falling_or_floating()
but I think this is the big pay-off.Testing
Ran the unit tests successfully.