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

PERF: Avoid MultiIndex conversion for IntervalIndex methods #24813

Open
jschendel opened this issue Jan 17, 2019 · 1 comment

Comments

@jschendel
Copy link
Member

commented Jan 17, 2019

There are a few IntervalIndex methods that convert to a MultiIndex as an intermediate step, and then use the associated MultiIndex method to compute the result. This likely introduces overhead that could be avoided via a more direct IntervalIndex implementation.

Methods that currently require a MultiIndex conversion:

  • IntervalIndex.is_monotonic (#25820)
  • IntervalIndex.is_monotonic_increasing (#25820)
  • IntervalIndex.is_monotonic_decreasing (#25820)
  • IntervalIndex.is_unique (#26391)
  • IntervalIndex._get_loc_only_exact_matches
  • IntervalIndex.union
  • IntervalIndex.intersection (#26225)
  • IntervalIndex.difference
  • IntervalIndex.symmetric_difference
@stevenbw

This comment has been minimized.

Copy link

commented Jan 20, 2019

@jschendel I will look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.