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

Reduce memory footprint #11

Open
ktnr opened this issue May 15, 2022 · 0 comments
Open

Reduce memory footprint #11

ktnr opened this issue May 15, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@ktnr
Copy link
Owner

ktnr commented May 15, 2022

Memory usage increases quite rapidly and can reach up to several hundreds of GB for hard instances. The complete search tree is kept in memory during the execution of the program. However, explored parts of the tree could be released to free up memory.

Doing so would require reorganizing node selection, which is currently managed via IDs, e.g. in backtracking:

Node& nodeToDeactivate = this->tree[nodeIdToDeactivate];

Implementing #4 would also help in this regard.

@ktnr ktnr added the enhancement New feature or request label May 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant