Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate whether re-encoding MultiIndex levels is beneficial #27498

Closed
qwhelan opened this issue Jul 21, 2019 · 0 comments · Fixed by #37221
Closed

Investigate whether re-encoding MultiIndex levels is beneficial #27498

qwhelan opened this issue Jul 21, 2019 · 0 comments · Fixed by #37221
Labels
MultiIndex Performance Memory or execution speed performance
Milestone

Comments

@qwhelan
Copy link
Contributor

qwhelan commented Jul 21, 2019

Follow up for #27495, where we handle the common case of MultiIndex being created from helper functions that ensure the levels are sorted. In order to handle the case of MultiIndex(codes=..., labels=...) and labels being individually unsorted, we likely need to re-encode that level. If that is performant, it would allow deleting a non-performant base case in MultiIndex.is_monotonic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MultiIndex Performance Memory or execution speed performance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants