perf: optimize get_element from O(n) to O(1) lookup #9
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
get_elementwas doing O(n) linear search instead of O(1) indexed lookupelements_by_idindex was being populated but not used effectivelyProblem
The
get_elementmethod retrieved an index fromelements_by_idbut then discarded it and did a linear search through the element vectors:Solution
Changed
elements_by_idto store(ElementType, usize)instead of justusize. Nowget_elementuses true O(1) lookup:Performance Impact
For a model with N elements:
This affects:
get_element- directly optimizedget_elements_by_type- callsget_elementinternallyget_elements_by_tag- callsget_elementinternallyget_children- callsget_elementinternallyOther Changes
enumerate()instead of manual index tracking inbuild_indexes(more idiomatic)Test plan
cargo clippypasses with no warningscargo fmt --checkpassesGenerated with Claude Code