Performance regression in 0.2 about umap HOT 3 OPEN

Leave it open for now -- I would like to be able to resolve such issues if I can, and perhaps with more time I might come up with an approach that could make this better. In the meantime you can use the new n_epochs parameter to speed up training time (at some loss of accuracy). For the dataset sizes you have I believe the effective default is 500; you could try dropping it to 200 and see if that helps.

from umap.

I suspect small dataset sizes are the issue here. The changes that were made for 0.2 were largely targetted at large dataset sizes, and correcting some issues in the resulting embedding. These changes are fundamentally necessary, but they may result in less perfomant (but more accurate!) results for small number of points, particularly when reducing to larger embedding dimensions as you are doing here.

Long story short: I think this may simply be a necessary performance regression for the kinds of data you have here. Sorry.

from umap.

That's interesting. It turned out that organizing small chunks of data many times works pretty well for our domain. I will have a look at the qualitative difference. So should this issue be closed?

from umap.