Potential regression induced by commit 6ef44f2

[rhshadrach]

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

• algos.isin.IsInFloat64.time_isin
  • dtype='Float64'; title='few_different_values'
  • dtype='Float64'; title='only_nans_values'
  • dtype=<class 'numpy.float64'>; title='few_different_values'
  • dtype=<class 'numpy.float64'>; title='only_nans_values'
• series_methods.Fillna.time_bfill
  • dtype='Int64'
  • dtype='datetime64[ns]'

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 @WillAyd

[WillAyd]

Thanks @rhshadrach . I think @DeaMariaLeon also found this via conbench - should be fixed from #57618