-
Notifications
You must be signed in to change notification settings - Fork 47
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
AAE mode taking too long for clustering and tsv file generation #232
Comments
Dear @microbiomix Thanks for the report. I'll need some more information:
I'm aware of some issues in the clustering algorithm when run on GPU with a lot of contigs. I think these have been resolved on master, but I'll take a look again |
Hi @jakobnissen, Thanks for the response.
|
Hi @jakobnissen , The AVAMB 4.1.3 installation via conda that I have, uses the following parameters in
So, it doesn't seem to be affected by the issues listed in #250 and links thereof? Any ideas where this slowdown might be originating? Should I try the master version for comparison to see if it is resolved there? |
@microbiomix any luck in resolving slow clustering issue with AAE mode? Adapted avamb workflow v4.1.3 and this step takes forever (even with gpu). Thanks |
Hello,
I am binning ~22M contigs from ~900 samples using AAE with default parameters. Training finished in 26 hours on an A100 GPU. Since then, it has been clustering and writing the
clusters.tsv
file extremely slowly. The first 18M contigs were written fast. From 18.4M contigs at the 12 hour mark, it was only at 18.8M contigs at the 18 hour mark. After 3.5 days, it is still at 20.5M contigs. I am not sure how long I will have to wait!Currently, GPU shows 25GB and 99% GPU utilized. Linux OS shows that vamb uses 1 CPU and 150GB memory.
For comparison, on the same server/GPU, VAE mode took 17 hours to train and 4.5 hours to cluster. I am using version 4.1.3.
Is this expected or am I doing something wrong? Happy to provide more info if needed.
Thanks a lot!
The text was updated successfully, but these errors were encountered: