TensorFlow Release 23.05
The NVIDIA container image of TensorFlow, release 23.05, is available on NGC.
Deprecation notice: As of the 23.04 release, TF1 is no longer released monthly. Known issues may be resolved in a future release based on customer demand.
Contents of the TensorFlow container
This container image includes the complete source of the NVIDIA version of TensorFlow in
/opt/tensorflow. It is prebuilt and installed as a system Python module.
To achieve optimum TensorFlow performance for image-based training, the container includes a sample script that demonstrates the efficient training of convolutional neural networks (CNNs). The sample script might need to be modified to fit your application. The container also includes the following:
- Ubuntu 22.04
23.05-tf2-py3container image contains Python 3.10.6.
- NVIDIA CUDA® 12.1.1
- NVIDIA cuBLAS 188.8.131.52
- cuTENSOR 184.108.40.206
- NVIDIA cuDNN 220.127.116.11
- NVIDIA NCCL 2.17.1
- NVIDIA DALI® 1.25.0
- NVIDIA RAPIDS™ 23.04
- Horovod 0.27.0
- OpenMPI 4.1.4+
- OpenUCX 1.14.0
- SHARP 3.0.2
- GDRCopy 2.3
- NVIDIA HPC-X 2.14
- rdma-core 36.0
- NVIDIA TensorRT™ 18.104.22.168
- TensorFlow-TensorRT (TF-TRT)
- Nsight Compute 2023.1.1.4
- Nsight Systems 2023.12
- JupyterLab 2.3.2 including Jupyter-TensorBoard
Release 23.05 is based on CUDA 12.1.1, which requires NVIDIA Driver release 530 or later. However, if you are running on a data center GPU (for example, T4 or any other data center GPU), you can use NVIDIA driver release 450.51 (or later R450), 470.57 (or later R470), 510.47 (or later R510), 515.65 (or later R515), 525.85 (or later R525), or 530.30 (or later R530). The CUDA driver's compatibility package only supports particular drivers. Thus, users should upgrade from all R418, R440, R460, and R520 drivers, which are not forward-compatible with CUDA 12.1. For a complete list of supported drivers, see the CUDA Application Compatibility topic. For more information, see CUDA Compatibility and Upgrades.
Key Features and Enhancements
This TensorFlow release includes the following key features and enhancements.
- As of the current 23.04 release, TF1 is no longer released monthly. Known issues may be solved in a future release based on customer demand.
- Starting with the 22.05 release, the TensorFlow 1 and 2 containers are available for the Arm SBSA platform.
For example, pulling the Docker image
nvcr.io/nvidia/tensorflow:22.05-tf2-py3Docker image on an Arm SBSA machine will automatically fetch the Arm-specific image.
- Support for Slurm PMI2 has been removed from the 22.01 release.
PMIX is supported by the container, but is not supported by default in Slurm. Users who depend on Slurm integration might need to configure Slurm for PMIX in the base OS as appropriate to their OS distribution (for Ubuntu 20.04, the required package is
NVIDIA TensorFlow Container Versions
The following table shows what versions of Ubuntu, CUDA, TensorFlow, and TensorRT are supported in each of the NVIDIA containers for TensorFlow. For older container versions, refer to the Frameworks Support Matrix.
Tensor Core Examples
The tensor core examples provided in GitHub focus on achieving the best performance and convergence by using the latest deep learning example networks and model scripts for training. Each example model trains with mixed precision Tensor Cores on NVIDIA Volta, therefore you can get results much faster than training without Tensor Cores. This model is tested against each NGC monthly container release to ensure consistent accuracy and performance over time.
- U-Net Medical model: This model is a convolutional neural network for 2D image segmentation.
This repository contains a U-Net implementation as described in the U-Net: Convolutional Networks for Biomedical Image Segmentation paper, without any alteration.
- Neural Collaborative Filtering (NCF) model: This model is a neural network that provides collaborative filtering based on implicit feedback, specifically, it provides product recommendations based on user and item interactions.
The training data for this model should contain a sequence of user ID, item ID pairs indicating that the specified user has interacted with, for example, was given a rating to or clicked on, the specified item.
- BERT model: Bidirectional Encoder Representations from Transformers (BERT) is a new method of pre-training language representations which obtains state-of-the-art results on a wide array of Natural Language Processing (NLP) tasks.
This model is based on BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding paper. BERT is an optimized version of Google's official implementation, which leverages mixed-precision arithmetic and Tensor Cores on V100 GPUs for faster training times and maintains target accuracy.
- An illegal memory access violation is exposed in TensorFlow 2.12 by the Electra model as implemented in JoC. The root cause is under investigation and will be fixed in a later release.
- Up to 99% perf regressions across all EfficientDet model configs.
- Collecting profiles with the native TensorFlow profiler may result in an application crash with the error “double free or corruption” due to a bug in the CUPTI library. This will be fixed in a future release.
- Some DLRM models may regress by 10-40%. We are currently investigating.
- A known performance regression of up to 50% affects some efficientnet models. The regression is inherited from upstream tensorflow and is still under investigation. It will be fixed in a subsequent release.
- The TF-TRT native segment fallback has a known issue that causes a crash.
This issue occurs when you use TF-TRT to convert a model with a subgraph that is then converted to TensorRT, but the conversion fails to build. Instead of falling back to native TensorFlow, TF-TRT will crash.
To prevent the conversion of an OP that causes a native segment fallback, use
- A known issue affects
aarch64 libgomp, which might sometimes cause
cannot allocate memory in static TLS blockerrors.
The workaround is to run the following command:
- In some configurations, the UNet3D model on A100 fails to initialize CUDNN due to an OOM. This can be fixed by increasing the GPU memory carveout with the environment variable
- There is a known performance regression in XLA that can cause performance regressions of up to 55% when training certain models such as EfficientNet with XLA enabled. The root cause is under investigation and will be fixed in a future release.
- On H100 NVLink systems using 2 GPUs for training, certain communication patterns can trigger a corner-case bug that manifests either as a hang or as an "illegal instruction" exception. A workaround for this case is to set the environment variable
NCCL_PROTO=^LL128. This issue will be addressed in an upcoming release.