Skip to content

Speed optimization: Block do not use their own Index objects #162

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

Closed
wesm opened this issue Sep 21, 2011 · 1 comment
Closed

Speed optimization: Block do not use their own Index objects #162

wesm opened this issue Sep 21, 2011 · 1 comment
Labels
Enhancement Internals Related to non-user accessible pandas implementation Performance Memory or execution speed performance Refactor Internal refactoring of code

Comments

@wesm
Copy link
Member

wesm commented Sep 21, 2011

A lot of time is spent in Index.new in some computations. I do not think there's an essential need to create Index objects when you could just have an array of integers referring back to the single Index having all the column names for the DataFrame. This would also facilitate renaming as renaming would only need to happen in one place. Definitely not a trivial refactor and would unfortunately break legacy pickles yet again. "For the greater good"

@jreback
Copy link
Contributor

jreback commented Apr 25, 2014

closed by #6745

@jreback jreback closed this as completed Apr 25, 2014
dan-nadler pushed a commit to dan-nadler/pandas that referenced this issue Sep 23, 2019
* Feature pandas-dev#162 - rename method for ChunkStore to allow symbol renaming
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Internals Related to non-user accessible pandas implementation Performance Memory or execution speed performance Refactor Internal refactoring of code
Projects
None yet
Development

No branches or pull requests

2 participants