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 Revit nodes that create a wrapper element
Current Performance
Currently every single time an element wrapper is created, an unnecessary assertion is performed to ensure that this wrapper is unique. This assertion is not logged or displayed to the user and from what I can tell, does not benefit them.
Proposed Performance
The best performance optimization is to avoid doing work :) . If there is no clear benefit to do this assertion every time, I propose we remove it from the release builds and only keep it there for debug builds. The performance benefit is small at face value but would add up over time in a large graph.
Dynamo Tuneup Comparison
On a model with ~55k elements collecting all elements 10 times improves performance about 8%, from 10.5 seconds to about 9.6 seconds on average.
Checklist