Skip to content

Conversation

mfeurer
Copy link
Contributor

@mfeurer mfeurer commented Nov 5, 2020

  • separate storage of data inside the ensemble builder into two dictionaries to separately store them on disk (one for scores and one for predictions). If we run over the allocated memory, we can still make use of the stored scores
  • do not stop the ensemble builder when the number of models to consider can no longer be reduced so that the ensemble builder can still delete models from the hard drive if necessary.
  • avoid unnecessary memory copies during ensemble construction
  • improve structure of temporary directories during unit testing

* separate storage of data inside the ensemble builder into two dictionaries to separately store them on disk (one for scores and one for predictions). If we run over the allocated memory, we can still make use of the stored scores
* do not stop the ensemble builder when the number of models to consider can no longer be reduced so that the ensemble builder can still delete models from the hard drive if necessary.
* avoid unnecessary memory copies during ensemble construction
* improve structure of temporary directories during unit testing
@mfeurer mfeurer merged commit d3aafbd into development Nov 5, 2020
@mfeurer mfeurer deleted the ensemble_selection_memory branch November 5, 2020 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant