Potential regression induced by commit eb55bca

[rhshadrach]

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

• timedelta.DatetimeAccessor.time_timedelta_days
• timedelta.DatetimeAccessor.time_timedelta_microseconds
• timedelta.DatetimeAccessor.time_timedelta_nanoseconds
• timedelta.DatetimeAccessor.time_timedelta_seconds
• tslibs.fields.TimeGetTimedeltaField.time_get_timedelta_field
  • size=1000000; field='microseconds'
  • size=1000000; field='nanoseconds'
  • size=1000000; field='seconds'
  • size=10000; field='microseconds'
  • size=10000; field='nanoseconds'
  • size=10000; field='seconds'
  • size=100; field='microseconds'
  • size=100; field='nanoseconds'
  • size=100; field='seconds'

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]

Awesome thanks. This was also discussed in #57951 - I believe @dontgoto has been taking a look

[rhshadrach]

Doh - closing as a duplicate.