|
|
@@ -8,9 +8,10 @@ This repository provides a script and recipe to train the FastPitch model to ach
|
|
|
* [Model architecture](#model-architecture)
|
|
|
* [Default configuration](#default-configuration)
|
|
|
* [Feature support matrix](#feature-support-matrix)
|
|
|
- * [Features](#features)
|
|
|
+ * [Features](#features)
|
|
|
* [Mixed precision training](#mixed-precision-training)
|
|
|
- * [Enabling mixed precision](#enabling-mixed-precision)
|
|
|
+ * [Enabling mixed precision](#enabling-mixed-precision)
|
|
|
+ * [Enabling TF32](#enabling-tf32)
|
|
|
* [Glossary](#glossary)
|
|
|
- [Setup](#setup)
|
|
|
* [Requirements](#requirements)
|
|
|
@@ -31,12 +32,15 @@ This repository provides a script and recipe to train the FastPitch model to ach
|
|
|
* [Inference performance benchmark](#inference-performance-benchmark)
|
|
|
* [Results](#results)
|
|
|
* [Training accuracy results](#training-accuracy-results)
|
|
|
- * [Training accuracy: NVIDIA DGX-1 (8x V100 16G)](#training-accuracy-nvidia-dgx-1-8x-v100-16g)
|
|
|
+ * [Training accuracy: NVIDIA DGX A100 (8x A100 40GB)](#training-accuracy-nvidia-dgx-a100-8x-a100-40gb)
|
|
|
+ * [Training accuracy: NVIDIA DGX-1 (8x V100 16GB)](#training-accuracy-nvidia-dgx-1-8x-v100-16gb)
|
|
|
* [Training performance results](#training-performance-results)
|
|
|
- * [Training performance: NVIDIA DGX-1 (8x V100 16G)](#training-performance-nvidia-dgx-1-8x-v100-16g)
|
|
|
+ * [Training performance: NVIDIA DGX A100 (8x A100 40GB)](#training-performance-nvidia-dgx-a100-8x-a100-40gb)
|
|
|
+ * [Training performance: NVIDIA DGX-1 (8x V100 16GB)](#training-performance-nvidia-dgx-1-8x-v100-16gb)
|
|
|
* [Expected training time](#expected-training-time)
|
|
|
* [Inference performance results](#inference-performance-results)
|
|
|
- * [Inference performance: NVIDIA DGX-1 (1x V100 16G)](#inference-performance-nvidia-dgx-1-1x-v100-16g)
|
|
|
+ * [Inference performance: NVIDIA DGX A100 (1x A100 40GB)](#inference-performance-nvidia-dgx-a100-gpu-1x-a100-40gb)
|
|
|
+ * [Inference performance: NVIDIA DGX-1 (1x V100 16GB)](#inference-performance-nvidia-dgx-1-1x-v100-16gb)
|
|
|
* [Inference performance: NVIDIA T4](#inference-performance-nvidia-t4)
|
|
|
- [Release notes](#release-notes)
|
|
|
* [Changelog](#changelog)
|
|
|
@@ -44,9 +48,9 @@ This repository provides a script and recipe to train the FastPitch model to ach
|
|
|
|
|
|
## Model overview
|
|
|
|
|
|
-FastPitch is one of two major components in a neural, text-to-speech (TTS) system:
|
|
|
+[FastPitch](https://arxiv.org/abs/2006.06873) is one of two major components in a neural, text-to-speech (TTS) system:
|
|
|
|
|
|
-* a mel-spectrogram generator such as FastPitch or [Tacotron 2](https://arxiv.org/abs/1712.05884), and
|
|
|
+* a mel-spectrogram generator such as [FastPitch](https://arxiv.org/abs/2006.06873) or [Tacotron 2](https://arxiv.org/abs/1712.05884), and
|
|
|
* a waveform synthesizer such as [WaveGlow](https://arxiv.org/abs/1811.00002) (see [NVIDIA example code](https://github.com/NVIDIA/DeepLearningExamples/tree/master/PyTorch/SpeechSynthesis/Tacotron2)).
|
|
|
|
|
|
Such two-component TTS system is able to synthesize natural sounding speech from raw transcripts.
|
|
|
@@ -55,16 +59,28 @@ The FastPitch model generates mel-spectrograms and predicts a pitch contour from
|
|
|
* modify the pitch contour to control the prosody,
|
|
|
* increase or decrease the fundamental frequency in a naturally sounding way, that preserves the perceived identity of the speaker,
|
|
|
* alter the pace of speech.
|
|
|
+Some of the capabilities of FastPitch are presented on the website with [samples](https://fastpitch.github.io/).
|
|
|
+
|
|
|
+Speech synthesized with FastPitch has state-of-the-art quality, and does not suffer from missing/repeating phrases like Tacotron2 does.
|
|
|
+This is reflected in Mean Opinion Scores ([details](https://arxiv.org/abs/2006.06873)).
|
|
|
+
|
|
|
+| Model | Mean Opinion Score (MOS) |
|
|
|
+|:----------|:-------------------------|
|
|
|
+| Tacotron2 | 3.946 ± 0.134 |
|
|
|
+| FastPitch | 4.080 ± 0.133 |
|
|
|
+
|
|
|
The FastPitch model is based on the [FastSpeech](https://arxiv.org/abs/1905.09263) model. The main differences between FastPitch and FastSpeech are that FastPitch:
|
|
|
* explicitly learns to predict the pitch contour,
|
|
|
-* pitch conditioning removes harsh sounding artifacts and provides faster convergence,
|
|
|
+* pitch conditioning removes harsh sounding artifacts and provides faster convergence,
|
|
|
* no need for distilling mel-spectrograms with a teacher model,
|
|
|
* [character durations](#glossary) are extracted with a pre-trained Tacotron 2 model.
|
|
|
|
|
|
+The FastPitch model is similar to [FastSpeech2](https://arxiv.org/abs/2006.04558), which has been developed concurrently. FastPitch averages pitch values over input tokens, and does not use additional conditioning such as the energy.
|
|
|
+
|
|
|
FastPitch is trained on a publicly
|
|
|
available [LJ Speech dataset](https://keithito.com/LJ-Speech-Dataset/).
|
|
|
|
|
|
-This model is trained with mixed precision using Tensor Cores on NVIDIA Volta and Turing GPUs. Therefore, researchers can get results from 2.0x to 2.7x2.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.
|
|
|
+This model is trained with mixed precision using Tensor Cores on Volta, Turing, and the NVIDIA Ampere GPU architectures. Therefore, researchers can get results from 2.0x to 2.7x 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.
|
|
|
|
|
|
### Model architecture
|
|
|
|
|
|
@@ -75,7 +91,7 @@ from raw text (Figure 1). The entire process is parallel, which means that all i
|
|
|
<img src="./img/fastpitch_model.png" alt="FastPitch model architecture" />
|
|
|
</p>
|
|
|
<p align="center">
|
|
|
- <em>Figure 1. Architecture of FastPitch. The model is composed of a bidirectional Transformer backbone (also known as a Transformer encoder), a pitch predictor, and a duration predictor. After passing through the first *N* Transformer blocks, encoding, the signal is augmented with pitch information and discretely upsampled. Then it goes through another set of *N* Transformer blocks, with the goal of
|
|
|
+ <em>Figure 1. Architecture of FastPitch (<a href=”https://arxiv.org/abs/2006.06873”>source</a>). The model is composed of a bidirectional Transformer backbone (also known as a Transformer encoder), a pitch predictor, and a duration predictor. After passing through the first *N* Transformer blocks, encoding, the signal is augmented with pitch information and discretely upsampled. Then it goes through another set of *N* Transformer blocks, with the goal of
|
|
|
smoothing out the upsampled signal, and constructing a mel-spectrogram.
|
|
|
</em>
|
|
|
</p>
|
|
|
@@ -108,7 +124,7 @@ The following features are supported by this model.
|
|
|
| :------------------------------------------------------------------|------------:|
|
|
|
|[AMP](https://nvidia.github.io/apex/amp.html) | Yes |
|
|
|
|[Apex DistributedDataParallel](https://nvidia.github.io/apex/parallel.html) | Yes |
|
|
|
-
|
|
|
+
|
|
|
#### Features
|
|
|
|
|
|
AMP - a tool that enables Tensor Core-accelerated training. For more information,
|
|
|
@@ -123,8 +139,8 @@ required.
|
|
|
|
|
|
### Mixed precision training
|
|
|
|
|
|
-Mixed precision is the combined use of different numerical precisions in a computational method. [Mixed precision](https://arxiv.org/abs/1710.03740) 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](https://developer.nvidia.com/tensor-cores) in the Volta and Turing architecture, 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.
|
|
|
+Mixed precision is the combined use of different numerical precisions in a computational method. [Mixed precision](https://arxiv.org/abs/1710.03740) 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](https://developer.nvidia.com/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](https://devblogs.nvidia.com/parallelforall/tag/fp16/) in the NVIDIA Deep Learning SDK.
|
|
|
@@ -145,9 +161,8 @@ step must be included when applying gradients. In PyTorch, loss scaling can be
|
|
|
easily applied by using the `scale_loss()` method provided by AMP. The scaling value
|
|
|
to be used can be [dynamic](https://nvidia.github.io/apex/fp16_utils.html#apex.fp16_utils.DynamicLossScaler) or fixed.
|
|
|
|
|
|
-By default, the `train_fastpitch.sh` script will
|
|
|
-launch mixed precision training with Tensor Cores. You can change this
|
|
|
-behaviour by removing the `--amp-run` flag from the `train.py` script.
|
|
|
+By default, the `scripts/train.sh` script will run in full precision.To launch mixed precision training with Tensor Cores, either set env variable `AMP=true`
|
|
|
+when using `scripts/train.sh`, or add `--amp` flag when directly executing `train.py` without the helper script.
|
|
|
|
|
|
To enable mixed precision, the following steps were performed:
|
|
|
* Import AMP from APEX:
|
|
|
@@ -157,14 +172,14 @@ To enable mixed precision, the following steps were performed:
|
|
|
|
|
|
* Initialize AMP:
|
|
|
```bash
|
|
|
- model, optimizer = amp.initialize(model, optimizer, opt_level="O1")
|
|
|
+ model, optimizer = amp.initialize(model, optimizer, opt_level="O1")
|
|
|
```
|
|
|
|
|
|
* If running on multi-GPU, wrap the model with `DistributedDataParallel`:
|
|
|
```bash
|
|
|
from apex.parallel import DistributedDataParallel as DDP
|
|
|
model = DDP(model)
|
|
|
- ```
|
|
|
+ ```
|
|
|
|
|
|
* Scale loss before backpropagation (assuming loss is stored in a variable
|
|
|
called `losses`):
|
|
|
@@ -179,7 +194,15 @@ called `losses`):
|
|
|
with optimizer.scale_loss(losses) as scaled_losses:
|
|
|
scaled_losses.backward()
|
|
|
```
|
|
|
+#### Enabling TF32
|
|
|
+
|
|
|
+TensorFloat-32 (TF32) is the new math mode in [NVIDIA A100](#https://www.nvidia.com/en-us/data-center/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](#https://blogs.nvidia.com/blog/2020/05/14/tensorfloat-32-precision-format/) blog post.
|
|
|
|
|
|
+TF32 is supported in the NVIDIA Ampere GPU architecture and is enabled by default.
|
|
|
|
|
|
### Glossary
|
|
|
|
|
|
@@ -195,7 +218,7 @@ The lowest vibration frequency of a periodic soundwave, for example, produced by
|
|
|
**Pitch**
|
|
|
A perceived frequency of vibration of music or sound.
|
|
|
|
|
|
-**Transformer**
|
|
|
+**Transformer**
|
|
|
The paper [Attention Is All You Need](https://arxiv.org/abs/1706.03762) introduces a novel architecture called Transformer, which repeatedly applies the attention mechanism. It transforms one sequence into another.
|
|
|
|
|
|
## Setup
|
|
|
@@ -206,20 +229,24 @@ The following section lists the requirements that you need to meet in order to s
|
|
|
|
|
|
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](https://github.com/NVIDIA/nvidia-docker)
|
|
|
-- [PyTorch 20.03-py3 NGC container](https://ngc.nvidia.com/registry/nvidia-pytorch)
|
|
|
+- [PyTorch 20.06-py3 NGC container](https://ngc.nvidia.com/registry/nvidia-pytorch)
|
|
|
or newer
|
|
|
-- [NVIDIA Volta](https://www.nvidia.com/en-us/data-center/volta-gpu-architecture/) or [Turing](https://www.nvidia.com/en-us/geforce/turing/) based GPU
|
|
|
+- supported GPUs:
|
|
|
+ - [NVIDIA Volta architecture](https://www.nvidia.com/en-us/data-center/volta-gpu-architecture/)
|
|
|
+ - [NVIDIA Turing architecture](https://www.nvidia.com/en-us/geforce/turing/)
|
|
|
+ - [NVIDIA Ampere architecture](https://www.nvidia.com/en-us/data-center/nvidia-ampere-gpu-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](https://docs.nvidia.com/ngc/ngc-getting-started-guide/index.html)
|
|
|
- [Accessing And Pulling From The NGC Container Registry](https://docs.nvidia.com/deeplearning/frameworks/user-guide/index.html#accessing_registry)
|
|
|
- [Running PyTorch](https://docs.nvidia.com/deeplearning/frameworks/pytorch-release-notes/running.html#running)
|
|
|
-
|
|
|
+
|
|
|
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](https://docs.nvidia.com/deeplearning/frameworks/support-matrix/index.html).
|
|
|
|
|
|
## Quick Start Guide
|
|
|
|
|
|
-To train your model using mixed precision with Tensor Cores or using FP32, perform the following steps using the default parameters of the FastPitch model on the LJSpeech 1.1 dataset. For the specifics concerning training and inference, see the [Advanced](#advanced) section.
|
|
|
+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 FastPitch model on the LJSpeech 1.1 dataset. For the specifics concerning training and inference, see the [Advanced](#advanced) section.
|
|
|
|
|
|
1. Clone the repository.
|
|
|
```bash
|
|
|
@@ -229,7 +256,7 @@ To train your model using mixed precision with Tensor Cores or using FP32, perfo
|
|
|
|
|
|
2. Build and run the FastPitch PyTorch NGC container.
|
|
|
|
|
|
- By default the container will use the first available GPU. Modify the script to include other available devices.
|
|
|
+ By default the container will use all available GPUs.
|
|
|
```bash
|
|
|
bash scripts/docker/build.sh
|
|
|
bash scripts/docker/interactive.sh
|
|
|
@@ -263,7 +290,7 @@ To train your model using mixed precision with Tensor Cores or using FP32, perfo
|
|
|
```
|
|
|
The training will produce a FastPitch model capable of generating mel-spectrograms from raw text.
|
|
|
It will be serialized as a single `.pt` checkpoint file, along with a series of intermediate checkpoints.
|
|
|
- The script is configured for 8x GPU with 16GB of memory. Consult [Training process](#training-process) and [example configs](#-training-performance-benchmark) to adjust to a different configuration.
|
|
|
+ The script is configured for 8x GPU with at least 16GB of memory. Consult [Training process](#training-process) and [example configs](#-training-performance-benchmark) to adjust to a different configuration or enable Automatic Mixed Precision.
|
|
|
|
|
|
5. Start validation/evaluation.
|
|
|
|
|
|
@@ -281,9 +308,10 @@ To train your model using mixed precision with Tensor Cores or using FP32, perfo
|
|
|
You can perform inference using the respective `.pt` checkpoints that are passed as `--fastpitch`
|
|
|
and `--waveglow` arguments:
|
|
|
```bash
|
|
|
- python inference.py --cuda --wn-channels 256 --amp-run \
|
|
|
+ python inference.py --cuda \
|
|
|
--fastpitch output/<FastPitch checkpoint> \
|
|
|
- --waveglow pretrained_models/waveglow/<waveglow checkpoint> \
|
|
|
+ --waveglow pretrained_models/waveglow/<WaveGlow checkpoint> \
|
|
|
+ --wn-channels 256 \
|
|
|
-i phrases/devset10.tsv \
|
|
|
-o output/wavs_devset10
|
|
|
```
|
|
|
@@ -293,7 +321,7 @@ To train your model using mixed precision with Tensor Cores or using FP32, perfo
|
|
|
`<output wav file name>|<utterance>`
|
|
|
```
|
|
|
To run
|
|
|
- inference in mixed precision, use the `--amp-run` flag. The output audio will
|
|
|
+ inference in mixed precision, use the `--amp` flag. The output audio will
|
|
|
be stored in the path specified by the `-o` argument. Consult the `inference.py` to learn more options, such as setting the batch size.
|
|
|
|
|
|
## Advanced
|
|
|
@@ -314,7 +342,7 @@ given model
|
|
|
|
|
|
The common scripts contain layer definitions common to both models
|
|
|
(`common/layers.py`), some utility scripts (`common/utils.py`) and scripts
|
|
|
-for audio processing (`common/audio_processing.py` and `common/stft.py`).
|
|
|
+for audio processing (`common/audio_processing.py` and `common/stft.py`).
|
|
|
|
|
|
In the root directory `./` of this repository, the `./train.py` script is used for
|
|
|
training while inference can be executed with the `./inference.py` script. The
|
|
|
@@ -332,7 +360,7 @@ together with their default values that are used to train FastPitch.
|
|
|
* `--epochs` - number of epochs (default: 1500)
|
|
|
* `--learning-rate` - learning rate (default: 0.1)
|
|
|
* `--batch-size` - batch size (default: 32)
|
|
|
-* `--amp-run` - use mixed precision training
|
|
|
+* `--amp` - use mixed precision training (default: disabled)
|
|
|
|
|
|
* `--pitch-predictor-loss-scale` - rescale the loss of the pitch predictor module to dampen
|
|
|
its influence on the shared feedforward transformer blocks
|
|
|
@@ -404,7 +432,7 @@ Follow these steps to use datasets different from the default LJSpeech dataset.
|
|
|
```
|
|
|
|
|
|
2. Prepare filelists with transcripts and paths to .wav files. They define training/validation split of the data (test is currently unused):
|
|
|
- ```
|
|
|
+ ```bash
|
|
|
./filelists
|
|
|
├── my_dataset_mel_ali_pitch_text_train_filelist.txt
|
|
|
└── my_dataset_mel_ali_pitch_text_val_filelist.txt
|
|
|
@@ -441,7 +469,7 @@ In order to use the prepared dataset, pass the following to the `train.py` scrip
|
|
|
--training-files ./filelists/my_dataset_mel_ali_pitch_text_train_filelist.txt \
|
|
|
--validation files ./filelists/my_dataset_mel_ali_pitch_text_val_filelist.txt
|
|
|
```
|
|
|
-
|
|
|
+
|
|
|
### Training process
|
|
|
|
|
|
FastPitch is trained to generate mel-spectrograms from raw text input. It uses short time Fourier transform (STFT)
|
|
|
@@ -453,14 +481,19 @@ reported in total output mel-spectrogram frames per second and recorded as `trai
|
|
|
The result is averaged over an entire training epoch and summed over all GPUs that were
|
|
|
included in the training.
|
|
|
|
|
|
-The `scripts/train.sh` script is configured for 8x GPU with 16GB of memory:
|
|
|
- ```
|
|
|
+The `scripts/train.sh` script is configured for 8x GPU with at least 16GB of memory:
|
|
|
+ ```bash
|
|
|
--batch-size 32
|
|
|
--gradient-accumulation-steps 1
|
|
|
```
|
|
|
-In a single accumulated step, there are `batch_size x gradient_accumulation_steps x #GPUs = 256` examples being processed in parallel. With a smaller number of GPUs, increase `--gradient_accumulation_steps` to keep this relation satisfied.
|
|
|
-
|
|
|
-Even though the training script uses all available GPUs, you can select the devices with the `CUDA_VISIBLE_DEVICES` environmental variable (see this [CUDA Pro Tip](https://devblogs.nvidia.com/cuda-pro-tip-control-gpu-visibility-cuda_visible_devices/) for more details).
|
|
|
+In a single accumulated step, there are `batch_size x gradient_accumulation_steps x GPUs = 256` examples being processed in parallel. With a smaller number of GPUs, increase `--gradient_accumulation_steps` to keep this relation satisfied, e.g., through env variables
|
|
|
+ ```bash
|
|
|
+ NGPU=4 GRAD_ACC=2 bash scripts/train.sh
|
|
|
+ ```
|
|
|
+With automatic mixed precision (AMP), a larger batch size fits in 16GB of memory:
|
|
|
+ ```bash
|
|
|
+ NGPU=4 GRAD_ACC=1 BS=64 AMP=true bash scripta/train.sh
|
|
|
+ ```
|
|
|
|
|
|
### Inference process
|
|
|
|
|
|
@@ -476,9 +509,6 @@ bash scripts/inference_example.sh
|
|
|
Examine the `inference_example.sh` script to adjust paths to pre-trained models,
|
|
|
and call `python inference.py --help` to learn all available options.
|
|
|
By default, synthesized audio samples are saved in `./output/audio_*` folders.
|
|
|
-The audio files <a href=”./audio/sample_fp16.wav>sample_fp16.wav</a> and <a href=”./audio/sample_fp32.wav>sample_fp32.wav</a>
|
|
|
- were generated using checkpoints from
|
|
|
-mixed precision and FP32 training, respectively.
|
|
|
|
|
|
FastPitch allows us to linearly adjust the pace of synthesized speech like [FastSpeech](https://arxiv.org/abs/1905.09263).
|
|
|
For instance, pass `--pace 0.5` for a twofold decrease in speed.
|
|
|
@@ -488,6 +518,7 @@ Pitch can be adjusted by transforming those pitch cues. A few simple examples ar
|
|
|
|
|
|
| Transformation | Flag | Samples |
|
|
|
| :-------------------------------------------|:------------------------------|:---------------------------------------:|
|
|
|
+| - | - | [link](./audio/sample_fp16.wav) |
|
|
|
| Amplify pitch wrt. to the mean pitch |`--pitch-transform-amplify` | [link](./audio/sample_fp16_amplify.wav) |
|
|
|
| Invert pitch wrt. to the mean pitch |`--pitch-transform-invert` | [link](./audio/sample_fp16_invert.wav) |
|
|
|
| Raise/lower pitch by <hz> |`--pitch-transform-shift <hz>` | [link](./audio/sample_fp16_shift.wav) |
|
|
|
@@ -497,6 +528,7 @@ Pitch can be adjusted by transforming those pitch cues. A few simple examples ar
|
|
|
The flags can be combined. Modify these functions directly in the `inference.py` script to gain more control over the final result.
|
|
|
|
|
|
You can find all the available options by calling `python inference.py --help`.
|
|
|
+More examples are presented on the website with [samples](https://fastpitch.github.io/).
|
|
|
|
|
|
## Performance
|
|
|
|
|
|
@@ -509,103 +541,21 @@ performance in training and inference mode.
|
|
|
|
|
|
To benchmark the training performance on a specific batch size, run:
|
|
|
|
|
|
-**FastPitch**
|
|
|
-
|
|
|
-* For 1 GPU
|
|
|
- * FP16
|
|
|
- ```bash
|
|
|
- python train.py \
|
|
|
- --amp-run \
|
|
|
- --batch-size 64 \
|
|
|
- --gradient-accumulation-steps 4 \
|
|
|
- --cuda \
|
|
|
- --cudnn-enabled \
|
|
|
- -o <output-dir> \
|
|
|
- --log-file <output-dir>/nvlog.json \
|
|
|
- --dataset-path <dataset-path> \
|
|
|
- --training-files <train-filelist-path> \
|
|
|
- --validation-files <val-filelist-path> \
|
|
|
- --pitch-mean-std-file <pitch-stats-path> \
|
|
|
- --epochs 10 \
|
|
|
- --warmup-steps 1000 \
|
|
|
- -lr 0.1 \
|
|
|
- --optimizer lamb \
|
|
|
- --gad-clip-thresh 1000.0 \
|
|
|
- --dur-predictor-loss-scale 0.1 \
|
|
|
- --pitch-predictor-loss-scale 0.1 \
|
|
|
- --weight-decay 1e-6
|
|
|
- ```
|
|
|
-
|
|
|
- * FP32
|
|
|
- ```bash
|
|
|
- python train.py \
|
|
|
- --batch-size 32 \
|
|
|
- --gradient-accumulation-steps 8 \
|
|
|
- --cuda \
|
|
|
- --cudnn-enabled \
|
|
|
- -o <output-dir> \
|
|
|
- --log-file <output-dir>/nvlog.json \
|
|
|
- --dataset-path <dataset-path> \
|
|
|
- --training-files <train-filelist-path> \
|
|
|
- --validation-files <val-filelist-path> \
|
|
|
- --pitch-mean-std-file <pitch-stats-path> \
|
|
|
- --epochs 10 \
|
|
|
- --warmup-steps 1000 \
|
|
|
- -lr 0.1 \
|
|
|
- --optimizer lamb \
|
|
|
- --grad-clip-thresh 1000.0 \
|
|
|
- --dur-predictor-loss-scale 0.1 \
|
|
|
- --pitch-predictor-loss-scale 0.1 \
|
|
|
- --weight-decay 1e-6
|
|
|
- ```
|
|
|
-
|
|
|
-* For multiple GPUs
|
|
|
- * FP16
|
|
|
- ```bash
|
|
|
- python -m multiproc train.py \
|
|
|
- --amp-run \
|
|
|
- --batch-size 32 \
|
|
|
- --gradient-accumulation-steps 1 \
|
|
|
- --cuda \
|
|
|
- --cudnn-enabled \
|
|
|
- -o <output-dir> \
|
|
|
- --log-file <output-dir>/nvlog.json \
|
|
|
- --dataset-path <dataset-path> \
|
|
|
- --training-files <train-filelist-path> \
|
|
|
- --validation-files <val-filelist-path> \
|
|
|
- --pitch-mean-std-file <pitch-stats-path> \
|
|
|
- --epochs 10 \
|
|
|
- --warmup-steps 1000 \
|
|
|
- -lr 0.1 \
|
|
|
- --optimizer lamb \
|
|
|
- --grad-clip-thresh 1000.0 \
|
|
|
- --dur-predictor-loss-scale 0.1 \
|
|
|
- --pitch-predictor-loss-scale 0.1 \
|
|
|
- --weight-decay 1e-6
|
|
|
- ```
|
|
|
+* NVIDIA DGX A100 (8x A100 40GB)
|
|
|
+ ```bash
|
|
|
+ AMP=true NGPU=1 BS=128 GRAD_ACC=2 EPOCHS=10 bash scripts/train.sh
|
|
|
+ AMP=true NGPU=8 BS=32 GRAD_ACC=1 EPOCHS=10 bash scripts/train.sh
|
|
|
+ NGPU=1 BS=128 GRAD_ACC=2 EPOCHS=10 bash scripts/train.sh
|
|
|
+ NGPU=8 BS=32 GRAD_ACC=1 EPOCHS=10 bash scripts/train.sh
|
|
|
+ ```
|
|
|
|
|
|
- * FP32
|
|
|
- ```bash
|
|
|
- python -m multiproc train.py \
|
|
|
- --batch-size 32 \
|
|
|
- --gradient-accumulation-steps 1
|
|
|
- --cuda \
|
|
|
- --cudnn-enabled \
|
|
|
- -o <output-dir> \
|
|
|
- --log-file <output-dir>/nvlog.json \
|
|
|
- --dataset-path <dataset-path> \
|
|
|
- --training-files <train-filelist-path> \
|
|
|
- --validation-files <val-filelist-path> \
|
|
|
- --pitch-mean-std-file <pitch-stats-path> \
|
|
|
- --epochs 10 \
|
|
|
- --warmup-steps 1000 \
|
|
|
- -lr 0.1 \
|
|
|
- --optimizer lamb \
|
|
|
- --grad-clip-thresh 1000.0 \
|
|
|
- --dur-predictor-loss-scale 0.1 \
|
|
|
- --pitch-predictor-loss-scale 0.1 \
|
|
|
- --weight-decay 1e-6
|
|
|
- ```
|
|
|
+* NVIDIA DGX-1 (8x V100 16GB)
|
|
|
+ ```bash
|
|
|
+ AMP=true NGPU=1 BS=64 GRAD_ACC=4 EPOCHS=10 bash scripts/train.sh
|
|
|
+ AMP=true NGPU=8 BS=32 GRAD_ACC=1 EPOCHS=10 bash scripts/train.sh
|
|
|
+ NGPU=1 BS=32 GRAD_ACC=8 EPOCHS=10 bash scripts/train.sh
|
|
|
+ NGPU=8 BS=32 GRAD_ACC=1 EPOCHS=10 bash scripts/train.sh
|
|
|
+ ```
|
|
|
|
|
|
Each of these scripts runs for 10 epochs and for each epoch measures the
|
|
|
average number of items per second. The performance results can be read from
|
|
|
@@ -616,36 +566,21 @@ the `nvlog.json` files produced by the commands.
|
|
|
To benchmark the inference performance on a specific batch size, run:
|
|
|
|
|
|
* For FP16
|
|
|
- ```
|
|
|
- python inference.py --cuda --amp-run \
|
|
|
- --fastpitch output/checkpoint_FastPitch_1500.pt \
|
|
|
- --waveglow pretrained_models/waveglow/waveglow_256channels_ljs_v3.pt \
|
|
|
- --wn-channels 256 \
|
|
|
- --include-warmup \
|
|
|
- --batch-size 1 \
|
|
|
- --repeats 1000 \
|
|
|
- --input phrases/benchmark_8_128.tsv \
|
|
|
- --log-file output/nvlog_inference.json
|
|
|
+ ```bash
|
|
|
+ AMP=true BS_SEQ=”1 4 8” REPEATS=100 bash scripts/inference_benchmark.sh
|
|
|
```
|
|
|
|
|
|
-* For FP32
|
|
|
- ```
|
|
|
- python inference.py --cuda \
|
|
|
- --fastpitch output/checkpoint_FastPitch_1500.pt \
|
|
|
- --waveglow pretrained_models/waveglow/waveglow_256channels_ljs_v3.pt \
|
|
|
- --wn-channels 256 \
|
|
|
- --include-warmup \
|
|
|
- --batch-size 1 \
|
|
|
- --pitch \
|
|
|
- --repeats 1000 \
|
|
|
- --input phrases/benchmark_8_128.tsv \
|
|
|
- --log-file output/nvlog_inference.json
|
|
|
+* For FP32 or TF32
|
|
|
+ ```bash
|
|
|
+ BS_SEQ=”1 4 8” REPEATS=100 bash scripts/inference_benchmark.sh
|
|
|
```
|
|
|
|
|
|
The output log files will contain performance numbers for the FastPitch model
|
|
|
-(number of output mel-spectrogram frames per second, reported as `generator_frames/s`)
|
|
|
-and for WaveGlow (number of output samples per second, reported as ` waveglow_samples/s`).
|
|
|
-The `inference.py` script will run a few warm-up iterations before running the benchmark. Inference will be averaged over 100 runs, as set by the `--repeats` flag.
|
|
|
+(number of output mel-spectrogram frames per second, reported as `generator_frames/s w
|
|
|
+`)
|
|
|
+and for WaveGlow (number of output samples per second, reported as ` waveglow_samples/s
|
|
|
+`).
|
|
|
+The `inference.py` script will run a few warm-up iterations before running the benchmark. Inference will be averaged over 100 runs, as set by the `REPEATS` env variable.
|
|
|
|
|
|
### Results
|
|
|
|
|
|
@@ -654,101 +589,144 @@ and accuracy in training and inference.
|
|
|
|
|
|
#### Training accuracy results
|
|
|
|
|
|
-##### Training accuracy: NVIDIA DGX-1 (8x V100 16G)
|
|
|
+##### Training accuracy: NVIDIA DGX A100 (8x A100 40GB)
|
|
|
|
|
|
-Our results were obtained by running the `./platform/train_fastpitch_{AMP,FP32}_DGX1_16GB_8GPU.sh` training script in the PyTorch 20.03-py3 NGC container on NVIDIA DGX-1 with 8x V100 16G GPUs.
|
|
|
+Our results were obtained by running the `./platform/DGXA100_FastPitch_{AMP,TF32}_8GPU.sh` training script in the 20.06-py3 NGC container on NVIDIA DGX A100 (8x A100 40GB) GPUs.
|
|
|
+
|
|
|
+| Loss (Model/Epoch) | 50 | 250 | 500 | 750 | 1000 | 1250 | 1500 |
|
|
|
+|:---------------------|------:|------:|------:|------:|------:|------:|------:|
|
|
|
+| FastPitch AMP | 0.503 | 0.252 | 0.214 | 0.202 | 0.193 | 0.188 | 0.184 |
|
|
|
+| FastPitch TF32 | 0.500 | 0.252 | 0.215 | 0.201 | 0.193 | 0.187 | 0.183 |
|
|
|
+
|
|
|
+##### Training accuracy: NVIDIA DGX-1 (8x V100 16GB)
|
|
|
+
|
|
|
+Our results were obtained by running the `./platform/DGX1_FastPitch_{AMP,FP32}_8GPU.sh` training script in the PyTorch 20.06-py3 NGC container on NVIDIA DGX-1 with 8x V100 16GB GPUs.
|
|
|
|
|
|
All of the results were produced using the `train.py` script as described in the
|
|
|
[Training process](#training-process) section of this document.
|
|
|
|
|
|
-| Loss (Model/Epoch) | 0 | 250 | 500 | 750 | 1000 | 1250 | 1500 |
|
|
|
-|:---------------------|-------:|------:|------:|------:|-------:|-------:|-------:|
|
|
|
-| FastPitch AMP | 35.094 | 0.254 | 0.216 | 0.201 | 0.193 | 0.187 | 0.184 |
|
|
|
-| FastPitch FP32 | 35.108 | 0.254 | 0.216 | 0.200 | 0.194 | 0.188 | 0.184 |
|
|
|
+| Loss (Model/Epoch) | 50 | 250 | 500 | 750 | 1000 | 1250 | 1500 |
|
|
|
+|:---------------------|------:|------:|------:|------:|------:|------:|------:|
|
|
|
+| FastPitch AMP | 0.499 | 0.250 | 0.211 | 0.198 | 0.190 | 0.184 | 0.180 |
|
|
|
+| FastPitch FP32 | 0.503 | 0.251 | 0.214 | 0.201 | 0.192 | 0.186 | 0.182 |
|
|
|
+
|
|
|
+
|
|
|
+<div style="text-align:center" align="center">
|
|
|
+ <img src="./img/loss.png" alt="Loss curves" />
|
|
|
+</div>
|
|
|
+
|
|
|
|
|
|
|
|
|
-<p align="center">
|
|
|
- <img src="./img/loss_fp16.png" alt="AMP loss curve" />
|
|
|
- <img src="./img/loss_fp32.png" alt="FP32 loss curve" />
|
|
|
-</p>
|
|
|
|
|
|
#### Training performance results
|
|
|
|
|
|
-##### Training performance: NVIDIA DGX-1 (8x V100 16G)
|
|
|
+##### Training performance: NVIDIA DGX A100 (8x A100 40GB)
|
|
|
+
|
|
|
+Our results were obtained by running the `./platform/DGXA100_FastPitch_{AMP,TF32}_8GPU.sh` training script in the 20.06-py3 NGC container on NVIDIA DGX A100 (8x A100 40GB) GPUs. Performance numbers, in output mel-scale spectrogram frames per second, were averaged over
|
|
|
+an entire training epoch.
|
|
|
+
|
|
|
+|Number of GPUs|Batch size per GPU|Frames/s with mixed precision|Frames/s with TF32|Speed-up with mixed precision|Multi-GPU strong scaling with mixed precision|Multi-GPU strong scaling with TF32|
|
|
|
+|---:|------------------:|--------:|-------:|-----:|-----:|-----:|
|
|
|
+| 1 | 128@AMP, 128@TF32 | 164955 | 113725 | 1.45 | 1.00 | 1.00 |
|
|
|
+| 4 | 64@AMP, 64@TF32 | 619527 | 435951 | 1.42 | 3.76 | 3.83 |
|
|
|
+| 8 | 32@AMP, 32@TF32 | 1040206 | 643569 | 1.62 | 6.31 | 5.66 |
|
|
|
+
|
|
|
+###### Expected training time
|
|
|
|
|
|
-Our results were obtained by running the `./platform/train_fastpitch_{AMP,FP32}_DGX1_16GB_8GPU.sh`
|
|
|
-training script in the PyTorch 20.03-py3 NGC container on NVIDIA DGX-1 with
|
|
|
-8x V100 16G GPUs. Performance numbers, in output mel-spectrograms per second, were averaged over
|
|
|
+The following table shows the expected training time for convergence for 1500 epochs:
|
|
|
+
|
|
|
+|Number of GPUs|Batch size per GPU|Time to train with mixed precision (Hrs)|Time to train with TF32 (Hrs)|Speed-up with mixed precision|
|
|
|
+|---:|-----------------:|-----:|-----:|-----:|
|
|
|
+| 1 |128@AMP, 128@TF32 | 18.5 | 26.6 | 1.44 |
|
|
|
+| 4 | 64@AMP, 64@TF32 | 5.5 | 7.5 | 1.36 |
|
|
|
+| 8 | 32@AMP, 32@TF32 | 3.6 | 5.3 | 1.47 |
|
|
|
+
|
|
|
+##### Training performance: NVIDIA DGX-1 (8x V100 16GB)
|
|
|
+
|
|
|
+Our results were obtained by running the `./platform/DGX1_FastPitch_{AMP,FP32}_8GPU.sh`
|
|
|
+training script in the PyTorch 20.06-py3 NGC container on NVIDIA DGX-1 with
|
|
|
+8x V100 16GB GPUs. Performance numbers, in output mel-scale spectrogram frames per second, were averaged over
|
|
|
an entire training epoch.
|
|
|
|
|
|
-|Number of GPUs|Batch size per GPU|Number of mels used with AMP|Number of mels used with FP32|Speed-up with AMP|Multi-GPU strong scaling with AMP|Multi-GPU strong scaling with FP32|
|
|
|
-|---:|---------------:|-------:|-------:|-----:|-----:|-----:|
|
|
|
-| 1 |64@AMP, 32@FP32 | 109769 | 40636 | 2.70 | 1.00 | 1.00 |
|
|
|
-| 4 |64@AMP, 32@FP32 | 361195 | 150921 | 2.39 | 3.29 | 3.71 |
|
|
|
-| 8 |32@AMP, 32@FP32 | 562136 | 278778 | 2.02 | 5.12 | 6.86 |
|
|
|
+|Number of GPUs|Batch size per GPU|Frames/s with mixed precision|Frames/s with FP32|Speed-up with mixed precision|Multi-GPU strong scaling with mixed precision|Multi-GPU strong scaling with FP32|
|
|
|
+|---:|----------------:|-------:|-------:|-----:|-----:|-----:|
|
|
|
+| 1 | 64@AMP, 32@FP32 | 110370 | 41066 | 2.69 | 1.00 | 1.00 |
|
|
|
+| 4 | 64@AMP, 32@FP32 | 402368 | 153853 | 2.62 | 3.65 | 3.75 |
|
|
|
+| 8 | 32@AMP, 32@FP32 | 570968 | 296767 | 1.92 | 5.17 | 7.23 |
|
|
|
|
|
|
To achieve these same results, follow the steps in the [Quick Start Guide](#quick-start-guide).
|
|
|
|
|
|
-##### Expected training time
|
|
|
+###### Expected training time
|
|
|
|
|
|
The following table shows the expected training time for convergence for 1500 epochs:
|
|
|
|
|
|
-|Number of GPUs|Batch size per GPU|Time to train with AMP (Hrs)|Time to train with FP32 (Hrs)|Speed-up with AMP|
|
|
|
-|---:|---------------:|-----:|-----:|-----:|
|
|
|
-| 1 |64@AMP, 32@FP32 | 27.0 | 73.7 | 2.73 |
|
|
|
-| 4 |64@AMP, 32@FP32 | 8.4 | 19.7 | 2.36 |
|
|
|
-| 8 |32@AMP, 32@FP32 | 5.5 | 10.8 | 1.97 |
|
|
|
-
|
|
|
+|Number of GPUs|Batch size per GPU|Time to train with mixed precision (Hrs)|Time to train with TF32 (Hrs)|Speed-up with mixed precision|
|
|
|
+|---:|-----------------:|-----:|-----:|-----:|
|
|
|
+| 1 | 64@AMP, 32@FP32 | 27.6 | 72.7 | 2.63 |
|
|
|
+| 4 | 64@AMP, 32@FP32 | 8.2 | 20.3 | 2.48 |
|
|
|
+| 8 | 32@AMP, 32@FP32 | 5.9 | 10.9 | 1.85 |
|
|
|
|
|
|
Note that most of the quality is achieved after the initial 500 epochs.
|
|
|
|
|
|
#### Inference performance results
|
|
|
|
|
|
The following tables show inference statistics for the FastPitch and WaveGlow
|
|
|
-text-to-speech system, gathered from 1000 inference runs, on a single V100 and a single T4,
|
|
|
-respectively. Latency is measured from the start of FastPitch inference to
|
|
|
+text-to-speech system, gathered from 100 inference runs. Latency is measured from the start of FastPitch inference to
|
|
|
the end of WaveGlow inference. Throughput is measured
|
|
|
as the number of generated audio samples per second at 22KHz. RTF is the real-time factor which denotes the number of seconds of speech generated in a second of wall-clock time, per input utterance.
|
|
|
-The used WaveGlow model is a 256-channel model [published on NGC](https://ngc.nvidia.com/catalog/models/nvidia:waveglow_ljs_256channels).
|
|
|
+The used WaveGlow model is a 256-channel model.
|
|
|
|
|
|
-Our results were obtained by running the `./scripts/inference_benchmark.sh` script in
|
|
|
-the PyTorch 20.03-py3 NGC container. Note that to reproduce the results,
|
|
|
-you need to provide pre-trained checkpoins for FastPitch and WaveGlow. Edit the script to provide your checkpoint filenames.
|
|
|
+Note that performance numbers are related to the length of input. The numbers reported below were taken with a moderate length of 128 characters. Longer utterances yield higher RTF, as the generator is fully parallel.
|
|
|
+##### Inference performance: NVIDIA DGX A100 (1x A100 40GB)
|
|
|
|
|
|
-Note that performance numbers are related to the length of input. The numbers reported below were taken with a moderate length of 128 characters. For longer utterances even better numbers are expected, as the generator is fully parallel.
|
|
|
+Our results were obtained by running the `./scripts/inference_benchmark.sh` inferencing benchmarking script in the 20.06-py3 NGC container on NVIDIA DGX A100 (1x A100 40GB) GPU.
|
|
|
|
|
|
-##### Inference performance: NVIDIA DGX-1 (1x V100 16G)
|
|
|
+|Batch size|Precision|Avg latency (s)|Latency tolerance interval 90% (s)|Latency tolerance interval 95% (s)|Latency tolerance interval 99% (s)|Throughput (samples/sec)|Speed-up with mixed precision|Avg RTF|
|
|
|
+|------:|------------:|--------------:|--------------:|--------------:|--------------:|----------------:|---------------:|----------:|
|
|
|
+| 1 | FP16 | 0.106 | 0.106 | 0.106 | 0.107 | 1,636,913 | 1.60 | 74.24 |
|
|
|
+| 4 | FP16 | 0.390 | 0.391 | 0.391 | 0.391 | 1,780,764 | 1.55 | 20.19 |
|
|
|
+| 8 | FP16 | 0.758 | 0.758 | 0.758 | 0.758 | 1,832,544 | 1.52 | 10.39 |
|
|
|
+| 1 | TF32 | 0.170 | 0.170 | 0.170 | 0.170 | 1,020,894 | - | 46.30 |
|
|
|
+| 4 | TF32 | 0.603 | 0.603 | 0.603 | 0.603 | 1,150,598 | - | 13.05 |
|
|
|
+| 8 | TF32 | 1.153 | 1.154 | 1.154 | 1.154 | 1,202,463 | - | 6.82 |
|
|
|
+
|
|
|
+##### Inference performance: NVIDIA DGX-1 (1x V100 16GB)
|
|
|
+
|
|
|
+Our results were obtained by running the `./scripts/inference_benchmark.sh` script in
|
|
|
+the PyTorch 20.06-py3 NGC container. The input utterance has 128 characters, synthesized audio has 8.05 s.
|
|
|
|
|
|
-The input utterance has 128 characters, synthesized audio has 8.05 s.
|
|
|
|
|
|
|Batch size|Precision|Avg latency (s)|Latency tolerance interval 90% (s)|Latency tolerance interval 95% (s)|Latency tolerance interval 99% (s)|Throughput (samples/sec)|Speed-up with mixed precision|Avg RTF|
|
|
|
|------:|------------:|--------------:|--------------:|--------------:|--------------:|----------------:|---------------:|----------:|
|
|
|
-| 1 | FP16 | 0.253 | 0.254 | 0.255 | 0.255 | 702,735 | 1.51 | 31.87 |
|
|
|
-| 4 | FP16 | 0.572 | 0.575 | 0.575 | 0.576 | 1,243,094 | 2.55 | 14.09 |
|
|
|
-| 8 | FP16 | 1.118 | 1.121 | 1.121 | 1.123 | 1,269,479 | 2.70 | 7.20 |
|
|
|
-| 1 | FP32 | 0.382 | 0.384 | 0.384 | 0.385 | 464,920 | - | 21.08 |
|
|
|
-| 4 | FP32 | 1.458 | 1.461 | 1.461 | 1.462 | 486,756 | - | 5.52 |
|
|
|
-| 8 | FP32 | 3.015 | 3.023 | 3.024 | 3.027 | 470,741 | - | 2.67 |
|
|
|
-
|
|
|
+| 1 | FP16 | 0.193 | 0.194 | 0.194 | 0.194 | 902,960 | 2.35 | 40.95 |
|
|
|
+| 4 | FP16 | 0.610 | 0.613 | 0.613 | 0.614 | 1,141,207 | 2.78 | 12.94 |
|
|
|
+| 8 | FP16 | 1.157 | 1.161 | 1.161 | 1.162 | 1,201,684 | 2.68 | 6.81 |
|
|
|
+| 1 | FP32 | 0.453 | 0.455 | 0.456 | 0.457 | 385,027 | - | 17.46 |
|
|
|
+| 4 | FP32 | 1.696 | 1.703 | 1.705 | 1.707 | 411,124 | - | 4.66 |
|
|
|
+| 8 | FP32 | 3.111 | 3.118 | 3.120 | 3.122 | 448,275 | - | 2.54 |
|
|
|
|
|
|
##### Inference performance: NVIDIA T4
|
|
|
|
|
|
+Our results were obtained by running the `./scripts/inference_benchmark.sh` script in
|
|
|
+the PyTorch 20.06-py3 NGC container.
|
|
|
The input utterance has 128 characters, synthesized audio has 8.05 s.
|
|
|
|
|
|
|Batch size|Precision|Avg latency (s)|Latency tolerance interval 90% (s)|Latency tolerance interval 95% (s)|Latency tolerance interval 99% (s)|Throughput (samples/sec)|Speed-up with mixed precision|Avg RTF|
|
|
|
-|------:|------------:|--------------:|--------------:|--------------:|--------------:|----------------:|---------------:|----------:|
|
|
|
-| 1 | FP16 | 0.952 | 0.958 | 0.960 | 0.962 | 186,349 | 1.30 | 8.45 |
|
|
|
-| 4 | FP16 | 4.187 | 4.209 | 4.213 | 4.221 | 169,473 | 1.21 | 1.92 |
|
|
|
-| 8 | FP16 | 7.799 | 7.824 | 7.829 | 7.839 | 181,978 | 1.38 | 1.03 |
|
|
|
-| 1 | FP32 | 1.238 | 1.245 | 1.247 | 1.250 | 143,292 | - | 6.50 |
|
|
|
-| 4 | FP32 | 5.083 | 5.109 | 5.114 | 5.124 | 139,613 | - | 1.58 |
|
|
|
-| 8 | FP32 | 10.756 | 10.797 | 10.805 | 10.820 | 131,951 | - | 0.75 |
|
|
|
-
|
|
|
+|-----:|-------:|----------:|--------:|--------:|--------:|-------------:|----------:|------:|
|
|
|
+| 1 | FP16 | 0.533 | 0.540 | 0.541 | 0.543 | 326,471 | 2.56 | 14.81 |
|
|
|
+| 4 | FP16 | 2.292 | 2.302 | 2.304 | 2.308 | 304,283 | 2.38 | 3.45 |
|
|
|
+| 8 | FP16 | 4.564 | 4.578 | 4.580 | 4.585 | 305,568 | 1.99 | 1.73 |
|
|
|
+| 1 | FP32 | 1.365 | 1.383 | 1.387 | 1.394 | 127,765 | - | 5.79 |
|
|
|
+| 4 | FP32 | 5.192 | 5.214 | 5.218 | 5.226 | 134,309 | - | 1.52 |
|
|
|
+| 8 | FP32 | 9.09 | 9.11 | 9.114 | 9.122 | 153,434 | - | 0.87 |
|
|
|
|
|
|
## Release notes
|
|
|
|
|
|
### Changelog
|
|
|
|
|
|
+June 2020
|
|
|
+- Updated performance tables to include A100 results
|
|
|
+
|
|
|
May 2020
|
|
|
- Initial release
|
|
|
|