Skip to content

bug in groupby when key space exceeds int64 bounds #9380

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
Jan 31, 2015

Conversation

behzadnouri
Copy link
Contributor

closes #9096

also improves performance when there is int64 overflow; complete groupby benchmarks here.

-------------------------------------------------------------------------------
Test name                                    | head[ms] | base[ms] |  ratio   |
-------------------------------------------------------------------------------
groupby_int64_overflow                       | 637.6967 | 3021.1190 |   0.2111 |
-------------------------------------------------------------------------------

Ratio < 1.0 means the target commit is faster then the baseline.
Seed used: 1234

Target [d6e3cb7] : bug in groupby when key space exceeds int64 bounds
Base   [391f46a] : BUG: allow for empty SparseSeries SparsePanel constructors (GH9272)

@jreback
Copy link
Contributor

jreback commented Jan 31, 2015

@behzadnouri this looks gr8! thanks

jreback added a commit that referenced this pull request Jan 31, 2015
bug in groupby when key space exceeds int64 bounds
@jreback jreback merged commit 9f439f0 into pandas-dev:master Jan 31, 2015
@behzadnouri behzadnouri deleted the i8grby branch February 7, 2015 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Groupby "negative dimensions are not allowed" error and bad key behaviour when there are NaNs values.
2 participants