sokrypton / sokrypton/ColabFold

How to make colabfold_batch use more CPU cores for large ensemble generation?

Open
#826 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
2.9k
Forks
747
PR merge metrics
No merged PRs in 30d

Description

Hi,

I am running colabfold_batch inside a Docker container as part of a webserver pipeline.

We are trying to generate a large ensemble of models for one protein. In one test, we used n_models=1500, but the job ran for about 5 days and did not finish, so it had to be canceled.

During the run, we noticed that only about 6–9 CPUs were being used, even though 64 CPUs were available to the container.

My questions are:

  1. Is there a recommended way to make colabfold_batch's use more CPU cores during the modeling/post-MSA steps?
  2. Are there specific flags or environment variables for controlling CPU/thread usage?
  3. For large ensemble generation, is it better to split the job into many smaller colabfold_batch runs instead of one run with a very large n_models value?

Any advice would be very helpful.

Thank you!

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

Start at the colabfold_batch entry point and review how Docker CPU allocation and the modeling/post-MSA steps affect thread usage. Compare a large n_models=1500 run with smaller runs; the issue is resolved when documented flags or environment variables, or a supported job-splitting recommendation, clearly explains how to use the available CPUs.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
bioinformatics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.