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.
Realistically, many projects have a large number of components that are used. Up to 100, 200 or even more depending on the scale.
So far, such a high number of components in the
Bitset
has caused problems. These simply checked the bits with a scalar loop. For a few used components this is fast, but for many it is quite slow and noticeable.Therefore this PR integrates vectorized
BitSet
methods to process a high number of used components faster. This is triggered only at a certain number, if the number of registered components exceeds this, the methods are executed vectorized. If they fall under it, the execution remains scalar. Since vectorization comes along with an overhead for few elements, the best of both sides is combined.