PERF: MultiIndex.memory_usage shouldn't trigger the index engine #58385
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.
Ignore the index engine when it isn't already cached.
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Reproducible Example
Calling
memory_usage()
can be unexpectedly slow when called on a big MultiIndex.Using the main branch:
Using this PR branch:
Side note:
index._engine.sizeof()
doesn't consider the content ofindex._engine.values
. If it should, a separate issue can be opened. In the example above, the additional unreported used memory would be: