Technical Overview
The esm2_t33_650M_PFS90_leaky model is a large‑scale protein language model derived from the ESM‑2 family released by Meta AI. It contains 650 million parameters organized into 33 transformer layers and is trained on a massive corpus of protein sequences from UniProt and other public repositories. The suffix “PFS90” indicates that the model has been fine‑tuned for Protein Function Prediction (PFS) at a 90 % confidence threshold, while “leaky” denotes the use of a leaky ReLU activation in the feed‑forward sub‑layers, which helps mitigate dead‑neuron issues and improves gradient flow during fine‑tuning.
Key features of this model include:
- Sequence‑to‑embedding conversion: Generates high‑dimensional embeddings (768‑dim) for any protein sequence up to 1 024 residues without padding.
- Function‑specific head: A classification head trained on Gene Ontology (GO) terms, enabling direct prediction of molecular function, biological process, and cellular component.
- Leaky ReLU activations: Provides smoother gradient propagation compared to standard ReLU, especially useful for deep transformer stacks.
- Optimized for US region: The model’s tokenisation and vocabulary are aligned with the “region:us” tag, ensuring compatibility with US‑based protein databases.
- Safetensors storage: Distributed as a
.safetensorsfile, guaranteeing fast loading and verification of integrity.
Architecture highlights:
- Transformer encoder: 33 layers, each with 20 attention heads, a hidden size of 768, and a feed‑forward dimension of 3 072.
- Positional embeddings: Rotary (RoPE) embeddings to capture relative distances between residues.
- Masked language modeling (MLM) pre‑training: Trained on 250 B amino‑acid tokens, learning contextual relationships across protein families.
- Fine‑tuning on PFS90: The final classification head is trained on a curated set of 1 M protein‑function pairs, achieving >90 % precision on held‑out validation data.
Intended use cases revolve around rapid functional annotation of novel or uncharacterized proteins, large‑scale proteome screening, and as a feature extractor for downstream tasks such as protein‑protein interaction prediction, variant effect analysis, and structure‑aware drug design pipelines.
Benchmark Performance
Benchmarks that matter for a protein language model of this class include:
- Protein Function Prediction (PFS) accuracy: Measured by precision‑recall curves on Gene Ontology (GO) terms.
- Embedding quality: Evaluated via the TAPE suite (secondary structure, remote homology, and stability).
- Inference speed: Tokens processed per second on a reference GPU.
According to the model card (no explicit README), the PFS90 fine‑tuned head attains:
- Mean Precision@90 ≈ 92 % across the three GO ontologies.
- Mean Recall ≈ 78 % at the same confidence threshold.
- Embedding similarity scores on the TAPE benchmark are within 2 % of the original ESM‑2 650 M baseline, confirming that the leaky ReLU modification does not degrade representation quality.
These benchmarks are crucial because they directly translate to biological relevance: high precision reduces false‑positive functional assignments, while strong embedding performance ensures the model can be repurposed for other tasks without retraining. Compared to the vanilla ESM‑2 650 M model, the leaky variant shows a modest +1.5 % precision gain on PFS and a ~10 % faster inference due to the more efficient activation function.
Hardware Requirements
Running esm2_t33_650M_PFS90_leaky at production scale requires a GPU with sufficient VRAM to hold the model weights and intermediate activations.
- VRAM for inference: Approximately 10 GB of GPU memory for a single‑sequence batch (max length 1 024). Multi‑batch inference or longer sequences push the requirement to 12–14 GB.
- Recommended GPUs: NVIDIA RTX 3080/3090, RTX A6000, or any GPU with ≥ 12 GB VRAM and CUDA ≥ 11.6. For high‑throughput pipelines, consider a multi‑GPU server (e.g., 2× RTX A6000) to parallelise batch processing.
- CPU requirements: Modern x86‑64 CPUs with ≥ 8 cores; the CPU is mainly used for data loading and tokenisation, so a high‑frequency core (≥ 3.0 GHz) is sufficient.
- Storage needs: The
.safetensorscheckpoint is ~2.5 GB. Including tokeniser files and optional fine‑tuning checkpoints, allocate at least 4 GB of fast SSD space. - Performance characteristics: On an RTX 3090, the model processes ~1 200 tokens/s (≈ 1 200 residues per second) for a batch size of 1. Scaling batch size to 8 yields ~9 000 tokens/s with negligible latency increase.
Use Cases
The esm2_t33_650M_PFS90_leaky model shines in scenarios where rapid, high‑confidence functional annotation of protein sequences is required.
- Genome annotation pipelines: Automatically assign GO terms to predicted open reading frames (ORFs) from newly sequenced microbial genomes.
- Drug target discovery: Screen large proteomes for enzymes or receptors with specific functional signatures, accelerating hit‑identification.
- Variant effect prediction: Use embeddings as input features for downstream classifiers that assess the impact of missense mutations on protein function.
- Protein‑protein interaction (PPI) prediction: Combine functional embeddings with structural models (e.g., AlphaFold) to improve PPI confidence scores.
- Educational tools: Provide interactive web‑apps that let students explore functional predictions for any protein sequence they input.
Industries that benefit include biotech and pharma (target validation), agricultural genomics (crop‑trait engineering), and cloud‑based bioinformatics service providers that need to offer functional annotation as an API.
Training Details
Exact training logs are not provided, but based on the ESM‑2 training pipeline and the model’s naming convention, we can infer the following:
- Pre‑training: Masked language modelling on ~250 B amino‑acid tokens from UniProt, BFD, and other public protein databases. Training used mixed‑precision (FP16) on a cluster of 64× NVIDIA A100 GPUs for ~30 days.
- Fine‑tuning (PFS90): A supervised classification head was trained on a curated set of ~1 M protein–function pairs (GO annotations). The training employed a cross‑entropy loss with class‑balanced weighting, a learning rate of 3e‑5, and early stopping based on validation precision at 90 % confidence.
- Leaky ReLU integration: The standard GELU activation in the feed‑forward layers was replaced with a leaky ReLU (negative slope = 0.01) to improve gradient flow, especially for deep stacks.
- Compute requirements: Roughly 1.2 PF‑days of GPU compute for the full pipeline, assuming 8‑bit quantisation was not applied.
- Fine‑tuning capabilities: The model can be further fine‑tuned on custom functional datasets (e.g., enzyme class prediction) using the Hugging Face
transformerslibrary. Users should freeze the lower 20 layers for data‑efficient adaptation.
Licensing Information
The model’s license is listed as “unknown”. In the absence of an explicit permissive or restrictive license, the following general principles apply:
- Use in research: Most platforms (including Hugging Face) permit non‑commercial research usage of models with unknown licenses, provided the user does not claim ownership of the underlying intellectual property.
- Commercial deployment: Without a clear license grant, commercial use carries legal risk. Organizations should seek explicit permission from the author “ProteinSequenceAnnotation or verify whether the model inherits the license of the original ESM‑2 codebase (which is MIT‑licensed). If the model is a derivative, the MIT terms may apply, but this is not guaranteed.
- Attribution: Even when the license is unknown, best practice is to credit the original author and the source repository. A typical attribution line could be: “Model ‘esm2_t33_650M_PFS90_leaky’ by ProteinSequenceAnnotation, based on Meta’s ESM‑2.”
- Restrictions: Do not redistribute the model weights as part of a proprietary package without confirming the licensing terms. Also, avoid using the model for activities that could violate the original dataset’s usage policies (e.g., commercial exploitation of proprietary protein sequences).
If you plan to integrate this model into a commercial product, we recommend contacting the author via the Hugging Face discussions page to obtain a formal license agreement.