· 4 min read · Gaia Lab

4,400 protein complexes with Boltz-2: predicting how two proteins bind

An open diffusion model, from the AlphaFold 3 family, applied to thousands of protein pairs to predict the structure of the complex and the confidence of the binding. Fifteen jobs, two campaigns and a lesson on what each pair costs when the complexes grow.

Two chains of circles, one teal and one red, intertwined like two helices
Illustration generated for the series: two chains folding together.

Fourth instalment of Cluster X-ray and the line with the fewest jobs: fifteen. Also one of those that reserves the most GPU, because each job runs for days.

The question #

Knowing whether two proteins interact, and how, is one of the central questions of structural biology: it explains signalling pathways, drug targets and the effect of mutations. Determining it experimentally costs months per pair. The line uses structure prediction to estimate, at the scale of thousands of pairs, the structure of the complex that two proteins form and the confidence that the binding is real.

How it is approached #

The model is Boltz-2, an open diffusion model for biomolecular structure, successor to Boltz-1 and comparable to AlphaFold 3. The workflow is the same in both campaigns:

  1. Resolve the sequences of each pair (from a local cache, a shared FASTA or live UniProt) and write one description per unique physical pair.
  2. Predict each complex with Boltz-2, using the project’s remote multiple-sequence-alignment server and generating three diffusion samples per pair to estimate variability.
  3. Build the results table per row of the experimental design, with the model’s confidence scores for each pair.

The first campaign covered 2,534 pairs; the second, 1,907, of which some 1,650 were new. About 4,400 predictions in total. The experimental design is generated separately and does not change inside the jobs: pairs already predicted are skipped, so a campaign can be resumed as many times as needed without losing anything.

What is learned #

Besides the table of complexes and confidences, the line left behind a useful measurement for anyone planning a campaign like this: what a pair costs. The first estimate, written before measuring, assumed two minutes per pair on a 48 GB card. The observed rate over the first 2,533 pairs was 4 to 5 minutes (median 240 s, mean 304 s). And in the tail of the second campaign, on reaching the largest complexes, the mean rose to 21 minutes per pair. A factor of ten between the initial hypothesis and the reality of the large complexes, which the resumable design absorbed without losing any work.

With a single sequence of predictions per card and the alignments computed elsewhere, the GPU spends a good part of its time waiting. Computing the alignments locally or predicting several pairs in parallel per card are the two obvious levers if the line grows.

On the cluster #

15jobs442 hGPU hours reserved442 hCPU hours reserved13 Jul – 16 Sepperiod (2026)
Fifteen jobs between July and September. Eleven percent of the cluster’s GPU-hours.
Hours each launch ran (colour = final state)#01 · L40S · requested 120 h · failed#01 · L40S · requested 120 h · failed: 0 h0 h#02 · L40S · requested 120 h · completed#02 · L40S · requested 120 h · completed: 63.1 h63.1 h#03 · L40S · requested 120 h · timed out#03 · L40S · requested 120 h · timed out: 120 h120 h#04 · L40S · requested 120 h · completed#04 · L40S · requested 120 h · completed: 60.8 h60.8 h#05 · H100 NVL · requested 120 h · completed#05 · H100 NVL · requested 120 h · completed: 6.9 h6.9 h#06 · H100 NVL · requested 168 h · cancelled#06 · H100 NVL · requested 168 h · cancelled: 0.1 h0.1 h#07 · H100 NVL · requested 168 h · timed out#07 · H100 NVL · requested 168 h · timed out: 168 h168 h#08 · H100 NVL · requested 72 h · completed#08 · H100 NVL · requested 72 h · completed: 19.7 h19.7 h#09 · H100 NVL · requested 24 h · completed#09 · H100 NVL · requested 24 h · completed: 2.8 h2.8 h
Hours each launch ran, with the card and the time requested. The two that ran out of time were relaunched and carried on where they left off.

In the fifth instalment , LiDAR point clouds and individual trees.


Figures from Slurm accounting (reserved capacity, not measured usage) and the archived sbatch files. Anonymised post: no identifiable users, paths, emails or project names. Quotations are from the script comments.