Transformers documentation
Overview
Overview
Transformers provides multiple inference optimization techniques to make models fast, affordable, and accessible. Options include alternative attention mechanisms for reduced memory traffic, code compilation for faster execution, and optimized kernels for throughput. Stack these techniques for maximum performance.
For device setup and hardware-specific configuration, see the Hardware guides. Check which techniques are supported on your hardware before applying the optimizations below.
Help the user choose an optimization for their Transformers inference workload. First identify whether memory or speed becomes a problem while loading the model, processing long inputs, generating longer sequences, or serving concurrent requests. Use the matching guide below and check support for the user’s model and hardware before recommending a change.
- Ask for the model and revision, library versions, GPU and available VRAM, CPU RAM, input length, generation limit, batch size, and number of concurrent requests. Ask follow-up questions when missing details could change the recommendation, and state your assumptions.
- Use the point where the problem occurs to choose what to investigate. Check model weights and loading settings for load-time memory, the KV cache as generated sequences grow, attention allocations for long inputs, and per-request state and scheduling for concurrent requests. Treat weight quantization and KV-cache quantization as separate settings.
- Recommend one change at a time. Check model and hardware compatibility, then measure peak GPU memory, latency or throughput, and output quality on the same representative workload. Explain any reduction in input length, generation length, or concurrency as a workload tradeoff.
- Report the proposed configuration, the documentation that supports it, expected tradeoffs, unresolved compatibility questions, and a validation procedure. Separate measurements from estimates. If you cannot run the workload, say that fit and performance remain unverified.
Memory and speed are closely related but not the same. Shrinking your memory footprint makes a model “faster” because there is less data to move around. Pure speed optimizations don’t always reduce memory and sometimes increase usage. Choose the appropriate optimization based on your use case and hardware.
Use the table below to pick an optimization technique.
| Technique | Speed | Memory |
|---|---|---|
| Compilation | ✅ | |
| Attention backends | ✅ | ✅ |
| Kernels | ✅ | ✅ |
| Quantization | ✅ | ✅ |
| Caching | ✅ | ✅ |
| Parallelism | ✅ | |
| Continuous batching | ✅ |
This guide gives you a quick start on Transformers optimizations.
Compilation
torch.compile reduces Python overhead, fuses operations, and creates kernels tuned for your shapes and hardware. The first run warms it up and subsequent runs use the faster compiled path.
Pass a fixed size cache to generate() to trigger torch.compile automatically.
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM
tokenizer = AutoTokenizer.from_pretrained("Qwen/Qwen3-0.6B")
model = AutoModelForCausalLM.from_pretrained("Qwen/Qwen3-0.6B", dtype=torch.float16, device_map="auto")
input = tokenizer("The French Bread Law states", return_tensors="pt").to(model.device)
output = model.generate(**input, do_sample=False, max_new_tokens=20, cache_implementation="static")
tokenizer.batch_decode(output, skip_special_tokens=True)[0]Avoid calling
torch.compile(model)outside of generate() to prevent the model from recompiling every step.
Attention backends
Alternative attention backends lower memory traffic. For example, FlashAttention tiles attention computations and avoids large intermediate tensors to reduce memory footprint.
Set attn_implementation in from_pretrained() to load an optimized attention backend.
from transformers import AutoModelForCausalLM
model = AutoModelForCausalLM.from_pretrained("Qwen/Qwen3-0.6B", attn_implementation="flash_attention_2")Kernels
Kernels fuse operations to boost throughput and reduce memory usage. The Kernels library loads optimized compute kernels from the Hub in a flexible and version-safe way.
The example below loads an optimized FlashAttention-2 kernel without installing the package.
import torch
from transformers import AutoModelForCausalLM
model = AutoModelForCausalLM.from_pretrained(
"Qwen/Qwen3-0.6B", attn_implementation="kernels-community/flash-attn2"
)Quantization
Quantization shrinks the size of every parameter which lowers memory footprint and increases speed because you can do more operations.
Pass a quantization config to the quantization_config argument in from_pretrained(). Each quantization backend has a different config with different arguments. The example below quantizes a model to 4-bits and configures the computation dtype with the bitsandbytes backend.
import torch
from transformers import AutoModelForCausalLM, BitsAndBytesConfig
bnb_config = BitsAndBytesConfig(load_in_4bit=True, bnb_4bit_compute_dtype=torch.bfloat16)
model = AutoModelForCausalLM.from_pretrained(
"allenai/Olmo-3-7B-Think", quantization_config=bnb_config
)Caching
Caching speeds up generation by reusing past keys and values instead of recomputing them for every token. To offset and reduce the memory cost of storing past keys and values, Transformers supports offloading the cache to the CPU. Only the current layer remains on the GPU.
Use the cache_implementation argument in generate() to set a cache strategy.
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM
tokenizer = AutoTokenizer.from_pretrained("Qwen/Qwen3-0.6B")
model = AutoModelForCausalLM.from_pretrained(
"Qwen/Qwen3-0.6B", attn_implementation="kernels-community/flash-attn2"
)
inputs = tokenizer("The Le Décret Pain states that a baguette must,", return_tensors="pt")
outputs = model.generate(**inputs, do_sample=False, max_new_tokens=50, cache_implementation="offloaded")Parallelism
Parallelism distributes a model across devices so models too big for one device run fast. This approach uses more memory due to sharding overhead and communication to sync results.
Tensor parallelism splits a model layer across devices. Set the number of devices with DistributedConfig(tp_size=N) and pass it to from_pretrained() to enable it.
from transformers import AutoModelForCausalLM, DistributedConfig
distributed_config = DistributedConfig(tp_size=4)
model = AutoModelForCausalLM.from_pretrained(
"meta-llama/Meta-Llama-3-8B-Instruct",
distributed_config=distributed_config,
)
print(model._tp_plan)Continuous batching
Continuous batching maximizes throughput by keeping the GPU busy with dynamic scheduling and chunked prefill. Serving applications use it to process multiple incoming requests concurrently.
Use generate_batch() to enable continuous batching.
import torch
from transformers import AutoModelForCausalLM, AutoTokenizer
from transformers.generation import ContinuousBatchingConfig, GenerationConfig
model = AutoModelForCausalLM.from_pretrained(
"Qwen/Qwen3-0.6B",
attn_implementation="sdpa",
device_map="auto",
torch_dtype=torch.bfloat16,
)
tokenizer = AutoTokenizer.from_pretrained("Qwen/Qwen3-0.6B")
prompts = [
"The Le Décret Pain states that a baguette must",
"Explain gravity in one sentence.",
"Name the capital of France.",
]
inputs = [tokenizer.encode(p) for p in prompts]
generation_config = GenerationConfig(
max_new_tokens=32,
eos_token_id=tokenizer.eos_token_id,
pad_token_id=tokenizer.pad_token_id,
do_sample=False,
)
continuous_batching_config = ContinuousBatchingConfig(max_batch_tokens=512)
outputs = model.generate_batch(
inputs=inputs,
generation_config=generation_config,
continuous_batching_config=continuous_batching_config,
)
for request_id, output in outputs.items():
text = tokenizer.decode(output.generated_tokens, skip_special_tokens=True)
print(f"[{request_id}] {text}")