PERF: enhance MultiIndex.remove_unused_levels when no levels are unused #20703
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.
git diff upstream/master -u -- "*.py" | flake8 --diff
This uses
np.bincount
rather thanalgos.unique
to check if there are unused levels: since levels indexes are adjacent integers, the former is faster (~50% in my tests). It then fallbacks toalgos.unique
if there are unused levels.The result is that asv tests on
--bench reshape
giveThere is a penalty (of the same order of magnitude) for cases in which there are unused levels, but I think this is worth because:
--bench multiindex_object
(where the index inDuplicates
always has unused levels) do not find any change in performance