Closed
Description
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
([PERF] Get rid of MultiIndex conversion in IntervalIndex.is_monotonic methods #25820) -
IntervalIndex.is_monotonic_increasing
([PERF] Get rid of MultiIndex conversion in IntervalIndex.is_monotonic methods #25820) -
IntervalIndex.is_monotonic_decreasing
([PERF] Get rid of MultiIndex conversion in IntervalIndex.is_monotonic methods #25820) -
IntervalIndex.is_unique
([PERF] Get rid of MultiIndex conversion in IntervalIndex.is_unique #26391) -
Update: no longer existsIntervalIndex._get_loc_only_exact_matches
-
IntervalIndex.union
-
IntervalIndex.intersection
([PERF] Get rid of MultiIndex conversion in IntervalIndex.intersection #26225) -
IntervalIndex.difference
-
IntervalIndex.symmetric_difference