Reduce peak memory in UMAP.fit
/UMAP.fit_transform
#6323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reduces the peak GPU memory usage during a
UMAP.fit
call by releasing certain temporaries as soon as possible.This required splitting the
FuzzySimplSet::run
function into a few sub-functions and intermingling them within_get_graph
to let us drop the temporary arrays earlier. While I was at it, I noticed that_get_graph
and_get_graph_supervised
were almost identical, so I've merged these paths a bit to reduce duplication. There's a lot more duplication in here that could be cleaned up (and I went down that rabbit hole a bit before stopping myself), but for now I think this should be sufficient.On an input of 190 GiB this dropped 12 GiB off the peak, and moved the high point into the
SimplSetEmbed
routines instead of inFuzzySimplSet
. Further memory improvements will come in a later PR.