DeepLearningExamples/PyTorch/Segmentation/nnUNet/README.md

nnU-Net For PyTorch

This repository provides a script and recipe to train the nnU-Net model to achieve state-of-the-art accuracy and is tested and maintained by NVIDIA.

Table Of Contents

• Model overview
  • Model architecture
  • Default configuration
  • Feature support matrix
    • Features
  • Mixed precision training
    • Enabling mixed precision
    • TF32
  • Glossary
• Setup
  • Requirements
• Quick Start Guide
• Advanced
  • Scripts and sample code
  • Command-line options
  • Getting the data
    • Dataset guidelines
    • Multi-dataset
  • Training process
  • Inference process
• Performance
  • Benchmarking
    • Training performance benchmark
    • Inference performance benchmark
  • Results
    • Training accuracy results
      • Training accuracy: NVIDIA DGX A100 (8x A100 80G)
      • Training accuracy: NVIDIA DGX-1 (8x V100 16G)
    • Training performance results
      • Training performance: NVIDIA DGX A100 (8x A100 80G)
      • Training performance: NVIDIA DGX-1 (8x V100 16G)
    • Inference performance results
      • Inference performance: NVIDIA DGX A100 (1x A100 80G)
      • Inference performance: NVIDIA DGX-1 (1x V100 16G)
• Release notes
  • Changelog
  • Known issues

Model overview

The nnU-Net ("no-new-Net") refers to a robust and self-adapting framework for U-Net based medical image segmentation. This repository contains a nnU-Net implementation as described in the paper: nnU-Net: Self-adapting Framework for U-Net-Based Medical Image Segmentation.

The differences between this nnU-net and original model are:

• Dynamic selection of patch size is not supported, and it has to be set in data_preprocessing/configs.py file.
• Cascaded U-Net is not supported.
• The following data augmentations are not used: rotation, simulation of low resolution, gamma augmentation.

This model is trained with mixed precision using Tensor Cores on Volta, Turing, and the NVIDIA Ampere GPU architectures. Therefore, researchers can get results 2x faster than training without Tensor Cores, while experiencing the benefits of mixed precision training. This model is tested against each NGC monthly container release to ensure consistent accuracy and performance over time.

We developed the model using PyTorch Lightning, a new easy to use framework that ensures code readability and reproducibility without the boilerplate.

Model architecture

     The nnU-Net allows training two types of networks: 2D U-Net and 3D U-Net to perform semantic segmentation of 3D images, with high accuracy and performance.

The following figure shows the architecture of the 3D U-Net model and its different components. U-Net is composed of a contractive and an expanding path, that aims at building a bottleneck in its centremost part through a combination of convolution, instance norm and leaky relu operations. After this bottleneck, the image is reconstructed through a combination of convolutions and upsampling. Skip connections are added with the goal of helping the backward flow of gradients in order to improve the training.

Figure 1: The 3D U-Net architecture

Default configuration

All convolution blocks in U-Net in both encoder and decoder are using two convolution layers followed by instance normalization and a leaky ReLU nonlinearity. For downsampling we are using stride convolution whereas transposed convolution for upsampling.

All models were trained with RAdam optimizer, learning rate 0.001 and weight decay 0.0001. For loss function we use the average of cross-entropy and dice coefficient.

Early stopping is triggered if validation dice score wasn't improved during the last 100 epochs.

Used data augmentation: crop with oversampling the foreground class, mirroring, zoom, Gaussian noise, Gaussian blur, brightness.

Feature support matrix

The following features are supported by this model:

Feature	nnUNet
DALI	Yes
Automatic mixed precision (AMP)	Yes
Distributed data parallel (DDP)	Yes

Features

DALI

NVIDIA DALI - DALI is a library accelerating data preparation pipeline. To accelerate your input pipeline, you only need to define your data loader with the DALI library. For details, see example sources in this repository or see the DALI documentation

Automatic Mixed Precision (AMP)

This implementation uses native PyTorch AMP implementation of mixed precision training. It allows us to use FP16 training with FP32 master weights by modifying just a few lines of code.

DistributedDataParallel (DDP)

The model uses PyTorch Lightning implementation of distributed data parallelism at the module level which can run across multiple machines.

Mixed precision training

Mixed precision is the combined use of different numerical precisions in a computational method. Mixed precision training offers significant computational speedup by performing operations in half-precision format, while storing minimal information in single-precision to retain as much information as possible in critical parts of the network. Since the introduction of Tensor Cores in Volta, and following with both the Turing and Ampere architectures, significant training speedups are experienced by switching to mixed precision -- up to 3x overall speedup on the most arithmetically intense model architectures. Using mixed precision training requires two steps:

1. Porting the model to use the FP16 data type where appropriate.
2. Adding loss scaling to preserve small gradient values.

The ability to train deep learning networks with lower precision was introduced in the Pascal architecture and first supported in CUDA 8 in the NVIDIA Deep Learning SDK.

For information about:

• How to train using mixed precision, see the Mixed Precision Training paper and Training With Mixed Precision documentation.
• Techniques used for mixed precision training, see the Mixed-Precision Training of Deep Neural Networks blog.
• APEX tools for mixed precision training, see the NVIDIA Apex: Tools for Easy Mixed-Precision Training in PyTorch.

Enabling mixed precision

For training and inference, mixed precision can be enabled by adding the --amp flag. Mixed precision is using native PyTorch implementation.

TF32

TensorFloat-32 (TF32) is the new math mode in NVIDIA A100 GPUs for handling the matrix math also called tensor operations. TF32 running on Tensor Cores in A100 GPUs can provide up to 10x speedups compared to single-precision floating-point math (FP32) on Volta GPUs.

TF32 Tensor Cores can speed up networks using FP32, typically with no loss of accuracy. It is more robust than FP16 for models which require high dynamic range for weights or activations.

For more information, refer to the TensorFloat-32 in the A100 GPU Accelerates AI Training, HPC up to 20x blog post.

TF32 is supported in the NVIDIA Ampere GPU architecture and is enabled by default.

Glossary

Test time augmentation

Test time augmentation is an inference technique which averages predictions from augmented images with its prediction. As a result, predictions are more accurate, but with the cost of slower inference process. For nnU-Net, we use all possible flip combinations for image augmenting. Test time augmentation can be enabled by adding the --tta flag.

Setup

The following section lists the requirements that you need to meet in order to start training the nnU-Net model.

Requirements

This repository contains Dockerfile which extends the PyTorch NGC container and encapsulates some dependencies. Aside from these dependencies, ensure you have the following components:

• NVIDIA Docker
• PyTorch 21.02 NGC container
• Supported GPUs:
  • NVIDIA Volta architecture
  • NVIDIA Turing architecture
  • NVIDIA Ampere architecture

For more information about how to get started with NGC containers, see the following sections from the NVIDIA GPU Cloud Documentation and the Deep Learning Documentation:

• Getting Started Using NVIDIA GPU Cloud
• Accessing And Pulling From The NGC Container Registry
• Running PyTorch

For those unable to use the PyTorch NGC container, to set up the required environment or create your own container, see the versioned NVIDIA Container Support Matrix.

Quick Start Guide

To train your model using mixed or TF32 precision with Tensor Cores or using FP32, perform the following steps using the default parameters of the nnUNet model on the Medical Segmentation Decathlon dataset. For the specifics concerning training and inference, see the Advanced section.

1. Clone the repository.

Executing this command will create your local repository with all the code to run nnU-Net.

git clone https://github.com/NVIDIA/DeepLearningExamples
cd DeepLearningExamples/PyTorch/Segmentation/nnUNet

2. Build the nnU-Net PyTorch NGC container.

This command will use the Dockerfile to create a Docker image named nnunet, downloading all the required components automatically.

docker build -t nnunet .

The NGC container contains all the components optimized for usage on NVIDIA hardware.

3. Start an interactive session in the NGC container to run preprocessing/training/inference.

The following command will launch the container and mount the ./data directory as a volume to the /data directory inside the container, and ./results directory to the /results directory in the container.

mkdir data results
docker run -it --runtime=nvidia --shm-size=8g --ulimit memlock=-1 --ulimit stack=67108864 --rm -v ${PWD}/data:/data -v ${PWD}/results:/results nnunet:latest /bin/bash

4. Prepare BraTS dataset.

To download and preprocess the data run:

python download.py --task 01
python preprocess.py --task 01 --dim 3
python preprocess.py --task 01 --dim 2

Then ls /data should print:

01_3d 01_2d Task01_BrainTumour

For the specifics concerning data preprocessing, see the Getting the data section.

5. Start training.

Training can be started with:

python scripts/train.py --gpus <gpus> --fold <fold> --dim <dim> [--amp]

To see descriptions of the train script arguments run python scripts/train.py --help. You can customize the training process. For details, see the Training process section.

6. Start benchmarking.

The training and inference performance can be evaluated by using benchmarking scripts, such as:

python scripts/benchmark.py --mode {train,predict} --gpus <ngpus> --dim {2,3} --batch_size <bsize> [--amp] 

To see descriptions of the benchmark script arguments run python scripts/benchmark.py --help.

7. Start inference/predictions.

Inference can be started with:

python scripts/inference.py --data <path/to/data> --dim <dim> --fold <fold> --ckpt_path <path/to/checkpoint> [--amp] [--tta] [--save_preds]

Note: You have to prepare either validation or test dataset to run this script by running python preprocess.py --task 01 --dim {2,3} --exec_mode {val,test}. After preprocessing inside given task directory (e.g. /data/01_3d/ for task 01 and dim 3) it will create val or test directory with preprocessed data ready for inference. Possible workflow:

python preprocess.py --task 01 --dim 3 --exec_mode val
python scripts/inference.py --data /data/01_3d/val --dim 3 --fold 0 --ckpt_path <path/to/checkpoint> --amp --tta --save_preds

Then if you have labels for predicted images you can evaluate it with evaluate.py script. For example:

python evaluate.py --preds /results/preds_task_01_dim_3_fold_0_tta --lbls /data/Task01_BrainTumour/labelsTr

To see descriptions of the inference script arguments run python scripts/inference.py --help. You can customize the inference process. For details, see the Inference process section.

Now that you have your model trained and evaluated, you can choose to compare your training results with our Training accuracy results. You can also choose to benchmark yours performance to Training performance benchmark, or Inference performance benchmark. Following the steps in these sections will ensure that you achieve the same accuracy and performance results as stated in the Results section.

Advanced

The following sections provide greater details of the dataset, running training and inference, and the training results.

Scripts and sample code

In the root directory, the most important files are:

• main.py: Entry point to the application. Runs training, evaluation, inference or benchmarking.
• preprocess.py: Entry point to data preprocessing.
• download.py: Downloads given dataset from Medical Segmentation Decathlon.
• Dockerfile: Container with the basic set of dependencies to run nnU-Net.
• requirements.txt: Set of extra requirements for running nnU-Net.
• evaluate.py: Compare predictions with ground truth and get final score.

The data_preprocessing folder contains information about the data preprocessing used by nnU-Net. Its contents are:

• configs.py: Defines dataset configuration like patch size or spacing.
• preprocessor.py: Implements data preprocessing pipeline.
• convert2tfrec.py: Implements conversion from NumPy files to tfrecords.

The data_loading folder contains information about the data pipeline used by nnU-Net. Its contents are:

• data_module.py: Defines LightningDataModule used by PyTorch Lightning.
• dali_loader.py: Implements DALI data loader.

The models folder contains information about the building blocks of nnU-Net and the way they are assembled. Its contents are:

• layers.py: Implements convolution blocks used by U-Net template.
• metrics.py: Implements dice metric
• loss.py: Implements loss function.
• nn_unet.py: Implements training/validation/test logic and dynamic creation of U-Net architecture used by nnU-Net.
• unet.py: Implements the U-Net template.

The utils folder includes:

• utils.py: Defines some utility functions e.g. parser initialization.
• logger.py: Defines logging callback for performance benchmarking.

The notebooks folder includes:

• custom_dataset.ipynb: Shows instructions how to use nnU-Net for custom dataset.

Other folders included in the root directory are:

• images/: Contains a model diagram.
• scripts/: Provides scripts for training, benchmarking and inference of nnU-Net.

Command-line options

To see the full list of available options and their descriptions, use the -h or --help command-line option, for example:

python main.py --help

The following example output is printed when running the model:

usage: main.py [-h] [--exec_mode {train,evaluate,predict}] [--data DATA] [--results RESULTS] [--logname LOGNAME] [--task TASK] [--gpus GPUS] [--learning_rate LEARNING_RATE] [--gradient_clip_val GRADIENT_CLIP_VAL] [--negative_slope NEGATIVE_SLOPE] [--tta] [--amp] [--benchmark] [--residual] [--focal] [--sync_batchnorm] [--save_ckpt] [--nfolds NFOLDS] [--seed SEED] [--skip_first_n_eval SKIP_FIRST_N_EVAL] [--ckpt_path CKPT_PATH] [--fold FOLD] [--patience PATIENCE] [--lr_patience LR_PATIENCE] [--batch_size BATCH_SIZE] [--val_batch_size VAL_BATCH_SIZE] [--steps STEPS [STEPS ...]] [--profile] [--momentum MOMENTUM] [--weight_decay WEIGHT_DECAY]  [--save_preds] [--dim {2,3}] [--resume_training] [--factor FACTOR] [--num_workers NUM_WORKERS] [--min_epochs MIN_EPOCHS] [--max_epochs MAX_EPOCHS] [--warmup WARMUP] [--norm {instance,batch,group}] [--nvol NVOL] [--data2d_dim {2,3}] [--oversampling OVERSAMPLING] [--overlap OVERLAP] [--affinity {socket,single,single_unique,socket_unique_interleaved,socket_unique_continuous,disabled}] [--scheduler {none,multistep,cosine,plateau}] [--optimizer {sgd,radam,adam}] [--blend {gaussian,constant}] [--train_batches TRAIN_BATCHES] [--test_batches TEST_BATCHES]

optional arguments:
  -h, --help            show this help message and exit
  --exec_mode {train,evaluate,predict}
                        Execution mode to run the model (default: train)
  --data DATA           Path to data directory (default: /data)
  --results RESULTS     Path to results directory (default: /results)
  --logname LOGNAME     Name of dlloger output (default: None)
  --task TASK           Task number. MSD uses numbers 01-10 (default: None)
  --gpus GPUS           Number of gpus (default: 1)
  --learning_rate LEARNING_RATE
                        Learning rate (default: 0.001)
  --gradient_clip_val GRADIENT_CLIP_VAL
                        Gradient clipping norm value (default: 0)
  --negative_slope NEGATIVE_SLOPE
                        Negative slope for LeakyReLU (default: 0.01)
  --tta                 Enable test time augmentation (default: False)
  --amp                 Enable automatic mixed precision (default: False)
  --benchmark           Run model benchmarking (default: False)
  --residual            Enable residual block in encoder (default: False)
  --focal               Use focal loss instead of cross entropy (default: False)
  --sync_batchnorm      Enable synchronized batchnorm (default: False)
  --save_ckpt           Enable saving checkpoint (default: False)
  --nfolds NFOLDS       Number of cross-validation folds (default: 5)
  --seed SEED           Random seed (default: 1)
  --skip_first_n_eval SKIP_FIRST_N_EVAL
                        Skip the evaluation for the first n epochs. (default: 0)
  --ckpt_path CKPT_PATH
                        Path to checkpoint (default: None)
  --fold FOLD           Fold number (default: 0)
  --patience PATIENCE   Early stopping patience (default: 100)
  --lr_patience LR_PATIENCE
                        Patience for ReduceLROnPlateau scheduler (default: 70)
  --batch_size BATCH_SIZE
                        Batch size (default: 2)
  --val_batch_size VAL_BATCH_SIZE
                        Validation batch size (default: 4)
  --steps STEPS [STEPS ...]
                        Steps for multistep scheduler (default: None)
  --profile             Run dlprof profiling (default: False)
  --momentum MOMENTUM   Momentum factor (default: 0.99)
  --weight_decay WEIGHT_DECAY
                        Weight decay (L2 penalty) (default: 0.0001)
  --save_preds          Enable prediction saving (default: False)
  --dim {2,3}           UNet dimension (default: 3)
  --resume_training     Resume training from the last checkpoint (default: False)
  --factor FACTOR       Scheduler factor (default: 0.3)
  --num_workers NUM_WORKERS
                        Number of subprocesses to use for data loading (default: 8)
  --min_epochs MIN_EPOCHS
                        Force training for at least these many epochs (default: 30)
  --max_epochs MAX_EPOCHS
                        Stop training after this number of epochs (default: 10000)
  --warmup WARMUP       Warmup iterations before collecting statistics (default: 5)
  --norm {instance,batch,group}
                        Normalization layer (default: instance)
  --nvol NVOL           Number of volumes which come into single batch size for 2D model (default: 1)
  --data2d_dim {2,3}    Input data dimension for 2d model (default: 3)
  --oversampling OVERSAMPLING
                        Probability of crop to have some region with positive label (default: 0.33)
  --overlap OVERLAP     Amount of overlap between scans during sliding window inference (default: 0.5)
  --affinity {socket,single,single_unique,socket_unique_interleaved,socket_unique_continuous,disabled}
                        type of CPU affinity (default: socket_unique_interleaved)
  --scheduler {none,multistep,cosine,plateau}
                        Learning rate scheduler (default: none)
  --optimizer {sgd,radam,adam}
                        Optimizer (default: radam)
  --blend {gaussian,constant}
                        How to blend output of overlapping windows (default: gaussian)
  --train_batches TRAIN_BATCHES
                        Limit number of batches for training (used for benchmarking mode only) (default: 0)
  --test_batches TEST_BATCHES
                        Limit number of batches for inference (used for benchmarking mode only) (default: 0)

Getting the data

The nnU-Net model was trained on the Medical Segmentation Decathlon datasets. All datasets are in Neuroimaging Informatics Technology Initiative (NIfTI) format.

Dataset guidelines

To train nnU-Net you will need to preprocess your dataset as a first step with preprocess.py script. Run python scripts/preprocess.py --help to see descriptions of the preprocess script arguments.

For example to preprocess data for 3D U-Net run: python preprocess.py --task 01 --dim 3.

In data_preprocessing/configs.py for each Medical Segmentation Decathlon task there are defined: patch size, precomputed spacings and statistics for CT datasets.

The preprocessing pipeline consists of the following steps:

1. Cropping to the region of non-zero values.
2. Resampling to the median voxel spacing of their respective dataset (exception for anisotropic datasets where the lowest resolution axis is selected to be the 10th percentile of the spacings).
3. Padding volumes so that dimensions are at least as patch size.
4. Normalizing:
   • For CT modalities the voxel values are clipped to 0.5 and 99.5 percentiles of the foreground voxels and then data is normalized with mean and standard deviation from collected from foreground voxels.
   • For MRI modalities z-score normalization is applied.

Multi-dataset

It is possible to run nnUNet on custom dataset. If your dataset correspond to Medical Segmentation Decathlon (i.e. data should be NIfTi format and there should be dataset.json file where you need to provide fields: modality, labels and at least one of training, test) you need to perform the following:

1. Mount your dataset to /data directory.  

2. In data_preprocessing/config.py:

   • Add to the task_dir dictionary your dataset directory name. For example, for Brain Tumour dataset, it corresponds to "01": "Task01_BrainTumour".
   • Add the patch size that you want to use for training to the patch_size dictionary. For example, for Brain Tumour dataset it corresponds to "01_3d": [128, 128, 128] for 3D U-Net and "01_2d": [192, 160] for 2D U-Net. There are three types of suffixes _3d, _2d they correspond to 3D UNet and 2D U-Net.

3. Preprocess your data with preprocess.py scripts. For example, to preprocess Brain Tumour dataset for 2D U-Net you should run python preprocess.py --task 01 --dim 2.

If you have dataset in other format or you want customize data preprocessing or data loading see notebooks/custom_dataset.ipynb.

Training process

The model trains for at least --min_epochs and at most --max_epochs epochs. After each epoch evaluation, the validation set is done and validation loss is monitored for early stopping (see --patience flag). Default training settings are:

• RAdam optimizer with learning rate of 0.001 and weight decay 0.0001.
• Training batch size is set to 2 for 3D U-Net and 16 for 2D U-Net.

This default parametrization is applied when running scripts from the scripts/ directory and when running main.py without explicitly overriding these parameters. By default, the training is in full precision. To enable AMP, pass the --amp flag. AMP can be enabled for every mode of execution.

The default configuration minimizes a function L = (1 - dice_coefficient) + cross_entropy during training and reports achieved convergence as dice coefficient per class. The training, with a combination of dice and cross entropy has been proven to achieve better convergence than a training using only dice.

The training can be run directly without using the predefined scripts. The name of the training script is main.py. For example:

python main.py --exec_mode train --task 01 --fold 0 --gpus 1 --amp

Training artifacts will be saved to /results in the container. Some important artifacts are:

• /results/logs.json: Collected dice scores and loss values evaluated after each epoch during training on validation set.
• /results/checkpoints: Saved checkpoints. By default, two checkpoints are saved - one after each epoch ('last.ckpt') and one with the highest validation dice (e.g 'epoch=5.ckpt' for if highest dice was at 5th epoch).

To load the pretrained model provide --ckpt_path <path/to/checkpoint>.

Inference process

Inference can be launched by passing the --exec_mode predict flag. For example:

python main.py --exec_mode predict --task 01 --fold 0 --gpus 1 --amp --tta --save_preds --ckpt_path <path/to/checkpoint>

The script will then:

• Load the checkpoint from the directory specified by the <path/to/checkpoint> directory
• Run inference on the preprocessed validation dataset corresponding to fold 0
• Print achieved score to the console
• If --save_preds is provided then resulting masks in the NumPy format will be saved in the /results directory

Performance

The performance measurements in this document were conducted at the time of publication and may not reflect the performance achieved from NVIDIA’s latest software release. For the most up-to-date performance measurements, go to NVIDIA Data Center Deep Learning Product Performance.

Benchmarking

The following section shows how to run benchmarks to measure the model performance in training and inference modes.

Training performance benchmark

To benchmark training, run scripts/benchmark.py script with --mode train:

python scripts/benchmark.py --mode train --gpus <ngpus> --dim {2,3} --batch_size <bsize> [--amp] 

For example, to benchmark 3D U-Net training using mixed-precision on 8 GPUs with batch size of 2, run:

python scripts/benchmark.py --mode train --gpus 8 --dim 3 --batch_size 2 --amp

Each of these scripts will by default run 1 warm-up epoch and start performance benchmarking during the second epoch.

At the end of the script, a line reporting the best train throughput and latency will be printed.

Inference performance benchmark

To benchmark inference, run scripts/benchmark.py script with --mode predict:

python scripts/benchmark.py --mode predict --dim {2,3} --batch_size <bsize> [--amp]

For example, to benchmark inference using mixed-precision for 3D U-Net, with batch size of 4, run:

python scripts/benchmark.py --mode predict --dim 3 --amp --batch_size 4

Each of these scripts will by default run warm-up for 1 data pass and start inference benchmarking during the second pass.

At the end of the script, a line reporting the inference throughput and latency will be printed.

Results

The following sections provide details on how to achieve the same performance and accuracy in training and inference.

Training accuracy results

Training accuracy: NVIDIA DGX A100 (8x A100 80G)

Our results were obtained by running the python scripts/train.py --gpus {1,8} --fold {0,1,2,3,4} --dim {2,3} [--amp] training scripts and averaging results in the PyTorch 21.02 NGC container on NVIDIA DGX with (8x A100 80G) GPUs.

Dimension	GPUs	Batch size / GPU	Accuracy - mixed precision	Accuracy - FP32	Time to train - mixed precision	Time to train - TF32	Time to train speedup (TF32 to mixed precision)
2	1	64	73.002	73.390	98 min	150 min	1.536
2	8	64	72.916	73.054	17 min	23 min	1.295
3	1	2	74.408	74.402	118 min	221 min	1.869
3	8	2	74.350	74.292	27 min	46 min	1.775

Training accuracy: NVIDIA DGX-1 (8x V100 16G)

Our results were obtained by running the python scripts/train.py --gpus {1,8} --fold {0,1,2,3,4} --dim {2,3} [--amp] training scripts and averaging results in the PyTorch 21.02 NGC container on NVIDIA DGX-1 with (8x V100 16G) GPUs.

Dimension	GPUs	Batch size / GPU	Accuracy - mixed precision	Accuracy - FP32	Time to train - mixed precision	Time to train - FP32	Time to train speedup (FP32 to mixed precision)
2	1	64	73.316	73.200	175 min	342 min	1.952
2	8	64	72.886	72.954	43 min	52 min	1.230
3	1	2	74.378	74.324	228 min	667 min	2.935
3	8	2	74.29	74.378	62 min	141 min	2.301

Training performance results

Training performance: NVIDIA DGX A100 (8x A100 80G)

Our results were obtained by running the python scripts/benchmark.py --mode train --gpus {1,8} --dim {2,3} --batch_size <bsize> [--amp] training script in the NGC container on NVIDIA DGX A100 (8x A100 80G) GPUs. Performance numbers (in volumes per second) were averaged over an entire training epoch.

Dimension	GPUs	Batch size / GPU	Throughput - mixed precision [img/s]	Throughput - TF32 [img/s]	Throughput speedup (TF32 - mixed precision)	Weak scaling - mixed precision	Weak scaling - TF32
2	1	64	1064.46	678.86	1.568	N/A	N/A
2	1	128	1129.09	710.09	1.59	N/A	N/A
2	8	64	6477.99	4780.3	1.355	6.086	7.042
2	8	128	8163.67	5342.49	1.528	7.23	7.524
3	1	1	13.39	8.46	1.583	N/A	N/A
3	1	2	15.97	9.52	1.678	N/A	N/A
3	1	4	17.84	5.16	3.457	N/A	N/A
3	8	1	92.93	61.68	1.507	6.94	7.291
3	8	2	113.51	72.23	1.572	7.108	7.587
3	8	4	129.91	38.26	3.395	7.282	7.415

To achieve these same results, follow the steps in the Quick Start Guide.

Training performance: NVIDIA DGX-1 (8x V100 16G)

Our results were obtained by running the python scripts/benchmark.py --mode train --gpus {1,8} --dim {2,3} --batch_size <bsize> [--amp] training script in the PyTorch 21.02 NGC container on NVIDIA DGX-1 with (8x V100 16G) GPUs. Performance numbers (in volumes per second) were averaged over an entire training epoch.

Dimension	GPUs	Batch size / GPU	Throughput - mixed precision [img/s]	Throughput - FP32 [img/s]	Throughput speedup (FP32 - mixed precision)	Weak scaling - mixed precision	Weak scaling - FP32
2	1	64	575.11	277.93	2.069	N/A	N/A
2	1	128	612.32	268.28	2.282	N/A	N/A
2	8	64	4178.94	2149.46	1.944	7.266	7.734
2	8	128	4629.01	2087.25	2.218	7.56	7.78
3	1	1	7.68	2.11	3.64	N/A	N/A
3	1	2	8.27	2.49	3.321	N/A	N/A
3	1	4	8.5	OOM	N/A	N/A	N/A
3	8	1	56.4	16.42	3.435	7.344	7.782
3	8	2	62.46	19.46	3.21	7.553	7.815
3	8	4	64.46	OOM	N/A	7.584	N/A

To achieve these same results, follow the steps in the Quick Start Guide.

Inference performance results

Inference performance: NVIDIA DGX A100 (1x A100 80G)

Our results were obtained by running the python scripts/benchmark.py --mode predict --dim {2,3} --batch_size <bsize> [--amp] inferencing benchmarking script in the PyTorch 21.02 NGC container on NVIDIA DGX A100 (1x A100 80G) GPU.

FP16

Dimension	Batch size	Resolution	Throughput Avg [img/s]	Latency Avg [ms]	Latency 90% [ms]	Latency 95% [ms]	Latency 99% [ms]
2	64	4x192x160	3198.8	20.01	24.1	30.5	33.75
2	128	4x192x160	3587.89	35.68	36.0	36.08	36.16
3	1	4x128x128x128	47.16	21.21	21.56	21.7	22.5
3	2	4x128x128x128	47.59	42.02	53.9	56.97	77.3
3	4	4x128x128x128	53.98	74.1	91.18	106.13	143.18

TF32

Dimension	Batch size	Resolution	Throughput Avg [img/s]	Latency Avg [ms]	Latency 90% [ms]	Latency 95% [ms]	Latency 99% [ms]
2	64	4x192x160	2353.27	27.2	27.43	27.53	27.7
2	128	4x192x160	2492.78	51.35	51.54	51.59	51.73
3	1	4x128x128x128	34.33	29.13	29.41	29.52	29.67
3	2	4x128x128x128	37.29	53.63	52.41	60.12	84.92
3	4	4x128x128x128	22.98	174.09	173.02	196.04	231.03

Throughput is reported in images per second. Latency is reported in milliseconds per batch. To achieve these same results, follow the steps in the Quick Start Guide.

Inference performance: NVIDIA DGX-1 (1x V100 16G)

Our results were obtained by running the python scripts/benchmark.py --mode predict --dim {2,3} --batch_size <bsize> [--amp] inferencing benchmarking script in the PyTorch 21.02 NGC container on NVIDIA DGX-1 with (1x V100 16G) GPU.

FP16

Dimension	Batch size	Resolution	Throughput Avg [img/s]	Latency Avg [ms]	Latency 90% [ms]	Latency 95% [ms]	Latency 99% [ms]
2	64	4x192x160	1866.52	34.29	34.7	48.87	52.44
2	128	4x192x160	2032.74	62.97	63.21	63.25	63.32
3	1	4x128x128x128	27.52	36.33	37.03	37.25	37.71
3	2	4x128x128x128	29.04	68.87	68.09	76.48	112.4
3	4	4x128x128x128	30.23	132.33	131.59	165.57	191.64

FP32

Dimension	Batch size	Resolution	Throughput Avg [img/s]	Latency Avg [ms]	Latency 90% [ms]	Latency 95% [ms]	Latency 99% [ms]
2	64	4x192x160	1051.46	60.87	61.21	61.48	62.87
2	128	4x192x160	1051.68	121.71	122.29	122.44	122.6
3	1	4x128x128x128	9.87	101.34	102.33	102.52	102.86
3	2	4x128x128x128	9.91	201.91	202.36	202.77	240.45
3	4	4x128x128x128	10.0	399.91	400.94	430.72	466.62

Throughput is reported in images per second. Latency is reported in milliseconds per batch. To achieve these same results, follow the steps in the Quick Start Guide.

Release notes

Changelog

May 2021

• Add Triton Inference Server support
• Removed deep supervision, attention and drop block

March 2021

• Container updated to 21.02
• Change data format from tfrecord to npy and data loading for 2D

January 2021

• Initial release
• Add notebook with custom dataset loading

Known issues

There are no known issues in this release.