PERF: Index.difference

[lukemanley]

• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/v2.2.0.rst file if fixing a bug or adding a new feature.

asv continuous -f 1.1 upstream/main perf-index-difference -b index_object.SetDisjoint

       before           after         ratio
-      7.97±0.4ms       3.16±0.4ms     0.40  index_object.SetDisjoint.time_datetime_difference_disjoint

asv continuous -f 1.1 upstream/main perf-index-difference -b multiindex_object.Difference

       before           after         ratio
-      3.55±0.7ms       1.29±0.3ms     0.36  multiindex_object.Difference.time_difference('int')
-      3.79±0.5ms       1.20±0.2ms     0.32  multiindex_object.Difference.time_difference('datetime')

[mroeschke]

Thanks @lukemanley

[rhshadrach]

This patch may have induced a performance regression. If it was a necessary behavior change, this may have been expected and everything is okay.

Please check the links below. If any ASVs are parameterized, the combinations of parameters that a regression has been detected for appear as subbullets.

• index_object.SetDisjoint.time_datetime_difference_disjoint
• multiindex_object.Difference.time_difference
  • dtype='int'
  • dtype='datetime'
  • dtype='ea_int'
  • dtype='string'

Subsequent benchmarks may have skipped some commits. The link below lists the commits that are between the two benchmark runs where the regression was identified.

79067a7...0bdbc44