You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the nf-core/funcscan pipeline to assign taxonomy to contigs using MMseqs2 with the GTDB database. My contigs are around 100-200 MB in size, and I am running the pipeline on a machine with the following specs:
36 cores
256 GB RAM
Despite utilizing all available resources, mmseq2 takes more than 4 hours per sample and does not finish. I am wondering if this runtime is normal or if there are ways to optimize the process to make it faster.
Questions:
What are the common bottlenecks when running MMseqs2 with the GTDB database, and how can I address them?
What is the expected runtime for MMseqs2 on contigs of this size?
Are there specific MMseqs2 settings (e.g., sensitivity, database partitioning) that could help speed up the analysis without compromising too much accuracy?
Any advice or insights from your experience with MMseqs2 and GTDB would be appreciated!
The text was updated successfully, but these errors were encountered:
Hi soedinglab,
I am running the
nf-core/funcscan
pipeline to assign taxonomy to contigs using MMseqs2 with the GTDB database. My contigs are around 100-200 MB in size, and I am running the pipeline on a machine with the following specs:Despite utilizing all available resources,
mmseq2
takes more than 4 hours per sample and does not finish. I am wondering if this runtime is normal or if there are ways to optimize the process to make it faster.Questions:
Any advice or insights from your experience with MMseqs2 and GTDB would be appreciated!
The text was updated successfully, but these errors were encountered: