Skip to content

PERF: use NaT comparisons in int64/datetimelikes #11010 #11023

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

Merged
merged 1 commit into from
Sep 8, 2015

Conversation

jreback
Copy link
Contributor

@jreback jreback commented Sep 7, 2015

closes #11010

In [10]: %timeit gr['3rd'].count()
100 loops, best of 3: 15.1 ms per loop

In [11]: %timeit gr['3rd'].min()
100 loops, best of 3: 8.4 ms per loop

In [12]: %timeit gr['3rd'].max()
100 loops, best of 3: 8.47 ms per loop

In [13]: %timeit gr['3rd'].first()
100 loops, best of 3: 10.5 ms per loop

In [14]: %timeit gr['3rd'].last()
100 loops, best of 3: 10.3 ms per loop

@jreback jreback added Groupby Performance Memory or execution speed performance labels Sep 7, 2015
@jreback jreback added this to the 0.17.0 milestone Sep 7, 2015
@jreback
Copy link
Contributor Author

jreback commented Sep 7, 2015

cc @larvian
cc @behzadnouri

jreback added a commit that referenced this pull request Sep 8, 2015
PERF: use NaT comparisons in int64/datetimelikes #11010
@jreback jreback merged commit 76a4d99 into pandas-dev:master Sep 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Groupby Performance Memory or execution speed performance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PERF: NaT groups cause wrong path in grouping
1 participant