nf-core / nf-core/funcscan

How to speed up MMseqs2 taxonomy assignment with GTDB database on large contigs?

Open
#424 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Nextflow
Stars
119
Forks
40
Avg merge
2d 17h
Merged PRs (30d)
5

Description

Hi nf-core/funcscan,

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:

  1. What are the common bottlenecks when running MMseqs2 with the GTDB database, and how can I address them?
  2. What is the expected runtime for MMseqs2 on contigs of this size?
  3. 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!

Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue concerns the MMseqs2 taxonomy-assignment step in nf-core/funcscan, using the GTDB database on 100–200 MB contigs. Start by locating that pipeline step and reviewing its resource and MMseqs2 settings; done would mean identifying the bottleneck and documenting validated runtime or optimization guidance for the stated hardware.

Written by the indexing model from the issue text.

Assessment

Domain
bioinformatics, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.