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.

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

Reuse grower (and thus the splitter) instead of creating a new one #81

Open
NicolasHug opened this issue Dec 18, 2018 · 0 comments
Open
Labels
perf Computational performance issue or improvement

Comments

@NicolasHug
Copy link
Collaborator

A new grower (and a new SplittingContext) is created at each iteration which may cause a memory use peak on large datasets (#79).

Instead of instanciating a new grower, we could just reset it and reuse the allocated space.

See #79 (comment) to evaluate the changes

@NicolasHug NicolasHug added the perf Computational performance issue or improvement label Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf Computational performance issue or improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant