This document provides the release notes for training-nv-pytorch version 25.07.
Main features and bug fixes
Main features
-
Upgraded vllm to v0.9.2.
-
Added support for TransformerEngine v2.3.0+5de3e14 , peft v0.16.0, and diffusers v0.34.0.
Bug fixes
None for this release.
Component versions
|
Use cases |
Training/Inference |
|
Framework |
pytorch |
|
Requirements |
NVIDIA Driver release >= 575 |
|
Core components |
|
Assets
25.07
-
egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:25.07-serverless
VPC image
acs-registry-vpc.{region-id}.cr.aliyuncs.com/egslingjun/{image:tag}Replace{region-id}with the region where your Alibaba Cloud Container Compute Service (ACS) is activated (for example,cn-beijingorcn-wulanchabu).
Replace {image:tag} with the name and tag of the image.The inference-nv-pytorch:25.03-vllm0.8.2-pytorch2.6-cu124-20250328-serverless and inference-nv-pytorch:25.03-sglang0.4.4.post1-pytorch2.5-cu124-20250327-serverless images are compatible with ACS and Lingjun multi-tenant deployments only. It is not compatible with Lingjun single-tenant deployments.
The egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:25.07-serverless image is suitable for Alibaba Cloud Container Compute Service (ACS) and Lingjun multi-tenant deployments. It is not compatible with Lingjun single-tenant deployments.
Driver requirements
-
The 25.07 release is based on CUDA 12.8.0 and requires NVIDIA driver version 575 or later. However, if you run on a data center GPU (such as a T4 or any other data center GPU), you can also use NVIDIA driver versions 470.57 (or later R470), 525.85 (or later R525), 535.86 (or later R535), or 545.23 (or later R545).
-
The CUDA compatibility package supports only specific driver series. Therefore, you must upgrade from R418, R440, R450, R460, R510, R520, R530, R545, R555, and R560, because these driver series are not forward compatible with CUDA 12.8. For a complete list of supported drivers, see CUDA Application Compatibility. For more information, see CUDA Compatibility and Upgrades.
Key features and enhancements
PyTorch compilation optimization
torch.compile(), introduced in PyTorch 2.0, often delivers strong gains for small-scale, single-GPU workloads. But LLM training depends on GPU memory optimization and distributed frameworks such as FSDP or DeepSpeed, so torch.compile() may offer limited benefits or even degrade performance.
-
Control communication granularity in the DeepSpeed framework. This helps the compiler capture a more complete compute graph and apply broader compilation optimizations.
-
Use an optimized PyTorch build:
-
The PyTorch compiler frontend is improved to ensure that compilation succeeds even if a graph break occurs in the compute graph.
-
Pattern matching and dynamic shape support are strengthened to improve post-compilation performance.
-
With these optimizations, 8B-parameter LLM training typically achieves an end-to-end throughput gain of about 20%.
GPU memory optimization for recomputation
A predictive model for GPU memory overhead, built on large-scale performance data—including different models, clusters, and training parameter settings, as well as system metrics such as GPU memory utilization collected during benchmarking—recommends the optimal number of activation recomputation layers. This approach is integrated into PyTorch, allowing you to achieve the performance gains of GPU memory optimization with minimal effort. This feature is now supported in the DeepSpeed framework.
ACCL
ACCL is Alibaba Cloud’s high-performance communication library built for Lingjun. ACCL-N is the GPU-focused version. ACCL-N is a high-performance communication library customized from NVIDIA NCCL. It is fully compatible with NCCL, fixes issues in the upstream NCCL release, and includes performance and stability improvements.
End-to-end performance evaluation
Using the Cloud Native Platform (CNP) AI performance analysis tool, we conducted a comprehensive end-to-end performance comparison between this image and a standard base image using mainstream open-source models and framework configurations. Through ablation studies, we also evaluated the performance contribution of each optimization component to overall model training.
E2E performance contribution analysis of GPU core components
We conducted the following tests, based on version 25.07, on a multi-node GPU cluster to evaluate and compare end-to-end training performance. The comparison configurations include:
-
Base: NGC PyTorch image.
-
ACS AI image: Base+ACCL: Base image with the ACCL communication library.
-
ACS AI image: AC2+ACCL: Golden image with AC2 Base OS and no optimizations enabled.
-
ACS AI image: AC2+ACCL+CompilerOpt: Golden image with AC2 Base OS and only the torch compile optimization enabled.
-
ACS AI image: AC2+ACCL+CompilerOpt+CkptOpt: Golden image with AC2 Base OS and both torch compile and selective gradient checkpointing optimizations enabled.

Quick start
The following example shows how to pull the training-nv-pytorch image using Docker.
To use the training-nv-pytorch image in Alibaba Cloud Container Compute Service (ACS), select it from the Artifact Center on the workload creation page in the console, or specify the image reference in a YAML file.
1. Pull the image
docker pull egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:[tag]
2. Enable compilation and gradient checkpointing optimizations (Optional)
-
Enable compilation optimization
Use the Transformers Trainer API:
training_args = TrainingArguments( bf16=True, gradient_checkpointing=True, torch_compile=True ) -
Enable gradient checkpointing optimization
export CHECKPOINT_OPTIMIZATION=true
3. Start the container
The image includes ljperf, a built-in model training tool. This example shows how to start the container and run a training task.
LLM example
# Start and enter the container
docker run --rm -it --ipc=host --net=host --privileged egslingjun-registry.cn-wulanchabu.cr.aliyuncs.com/egslingjun/training-nv-pytorch:[tag]
# Run a training demo
ljperf benchmark --model deepspeed/llama3-8b
4. Usage notes
-
The image includes modifications to libraries such as PyTorch and DeepSpeed. Do not reinstall them.
-
In your DeepSpeed configuration, leave
zero_optimization.stage3_prefetch_bucket_sizeempty or set it toauto. -
The built-in
NCCL_SOCKET_IFNAMEenvironment variable must be adjusted depending on the use case:-
If a single pod requests 1, 2, 4, or 8 GPUs for a training/inference task, set
NCCL_SOCKET_IFNAME=eth0. This is the default setting. -
If a single pod requests all 16 GPUs on a host to use the high-performance network (HPN) for a training/inference task, set
NCCL_SOCKET_IFNAME=hpn0.
-
Known issues
None for this release.