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.
List of Affected Nodes/Modules
All nodes that wrap or create Revit elements
Current Performance
Every time an element is wrapped, we store its id and unique id. Then the native element is passed to the element binder and the id and unique id properties are fetched again. It didn't make sense to me to pay the cost of fetching those twice after already referencing them (plus also allocating the memory):
Proposed Performance
We should not pass the native element but the already extracted id and unique ids:
The cost is mostly from fetching the unique id/ Unfortunately, the performance benefit did not quite pan out the way I expected it to (should have reduced the get_UniqueId total cpu time by at least half)
Dynamo Tuneup Comparison
With a very basic graph that fetches 25k elements and creates 10k instances the performance gain is negligible and we go from 4.7 seconds on average down to 4.6:
Overall I am not entirely sure if this change is worth it due to the large code change.
Checklist