Performance in Boltz-2 NIM
NIM Accuracy
The Boltz-2 NIM is based on the state-of-the-art Boltz-2 architecture for biomolecular structure prediction. The NIM’s accuracy should match that of the reference implementation when using equivalent parameters and inputs.
Running on hardware that is not listed as supported in the prerequisites section may produce results that deviate from the expected accuracy.
The accuracy of the NIM is measured by structural quality metrics such as lddt. These scores help assess the reliability of the predicted structures.
Factors Affecting NIM Performance
The performance of the Boltz-2 NIM is determined by several key factors:
Hardware Factors
- Number and type of GPUs: More GPUs generally improve throughput for concurrent requests
- GPU memory: Larger proteins and complexes require more GPU memory
- Storage speed: Fast NVMe SSD storage improves model loading and caching performance
Input Complexity
- Sequence length: Runtime scales approximately quadratically with total sequence length
- Number of chains: Multi-chain complexes require more computation than single chains
- Ligands and constraints: Additional molecular components increase computational cost
Model Parameters
- Sampling steps: Higher values improve quality but significantly increase runtime
- Recycling steps: More iterations improve accuracy with modest runtime increase
- Diffusion samples: Multiple samples provide diversity but multiply computational cost
Performance Characteristics
Typical Runtimes
For reference, approximate runtimes on high-end hardware (8x NVIDIA H100 80GB):
Performance Testing
You can test basic performance and functionality with a simple protein structure prediction:
Expected Performance Baselines
For the test sequence above (~240 residues), you should expect:
- Runtime: 3-8 minutes on 4-8 NVIDIA A100/H100 GPUs
- Confidence score: Typically > 0.7 for well-folded proteins
- Memory usage: ~4-8 GB GPU memory per prediction
Performance Optimization Tips
-
For development/testing: Use faster settings
-
For production quality: Use higher quality settings
-
For batch processing: Submit multiple concurrent requests with default settings
-
For very large proteins (>1000 residues): Consider domain-based approaches or consult the literature for handling strategies
Troubleshooting Performance Issues
Common Issues and Solutions
- Out of memory errors: Reduce sequence length, decrease sampling steps, or use fewer concurrent requests
- Slow performance: Ensure fast storage (NVMe SSD), sufficient CPU cores (12+ per GPU), and adequate system RAM (32+ GB per GPU)
- Poor quality predictions: Increase sampling steps, recycling steps, or check input sequence quality
For detailed performance tuning guidance specific to your deployment, refer to the Optimization section.