Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove special columns from namedtuple in nate class #13

Open
pbrowne88 opened this issue Mar 13, 2020 · 0 comments
Open

Remove special columns from namedtuple in nate class #13

pbrowne88 opened this issue Mar 13, 2020 · 0 comments
Labels
optimization (optional) Non-critical improvements to memory/processor usage

Comments

@pbrowne88
Copy link
Member

Currently, all of the 'columns' passed into a nate object are stored in self.data, which can be very memory-inefficient.

If we keep the special columns (text, time, ID) separate, and package all of the non-special columns into the self.data object, we'll get the best of both worlds (easy compartmentalization in namespaces, memory efficiency)

Not critical unless we encounter memory bottlenecks.
@pbrowne88 pbrowne88 added the optimization (optional) Non-critical improvements to memory/processor usage label Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimization (optional) Non-critical improvements to memory/processor usage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pbrowne88