-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Performance regression in TimedeltaIndexing.time_get_loc #34510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Indexing
Related to indexing on series/frames, not to indexes themselves
Performance
Memory or execution speed performance
Regression
Functionality that used to work in a prior pandas version
Timedelta
Timedelta data type
Milestone
Comments
Looking at %prun results, about 40% of the change is accounted for by _validate_scalar |
Yeah that's the place we should focus.
Two proposals:
maybe |
TomAugspurger
added a commit
to TomAugspurger/pandas
that referenced
this issue
Jun 12, 2020
TomAugspurger
added a commit
to TomAugspurger/pandas
that referenced
this issue
Jun 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Indexing
Related to indexing on series/frames, not to indexes themselves
Performance
Memory or execution speed performance
Regression
Functionality that used to work in a prior pandas version
Timedelta
Timedelta data type
Setup:
See https://pandas.pydata.org/speed/pandas/#timedelta.TimedeltaIndexing.time_get_loc?commits=9929fca8-62c7dd3e
Happened somewhere between May 11 and May 27 (the gap in the benchmarks)
The text was updated successfully, but these errors were encountered: