Potential regression induced by PR #57534

[rhshadrach]

PR #57534 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.

• groupby.Apply.time_scalar_function_single_col
  • factor=5
• indexing.ChainIndexing.time_chained_indexing
  • mode='warn'
  • mode=None
• indexing.NumericSeriesIndexing.time_getitem_array
  • dtype=<class 'numpy.int64'>; index_structure='unique_monotonic_inc'
• indexing.NumericSeriesIndexing.time_iloc_array
  • dtype=<class 'numpy.int64'>; index_structure='unique_monotonic_inc'
• indexing.NumericSeriesIndexing.time_loc_array
  • dtype=<class 'numpy.int64'>; index_structure='unique_monotonic_inc'
• timedelta.TimedeltaIndexing.time_union

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.

Commit Range

cc @mroeschke

[mroeschke]

Since this is closely related to #57622, going to close for the same reason