mirror of https://github.com/hpcaitech/ColossalAI
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
65 lines
3.0 KiB
65 lines
3.0 KiB
# Gradient Clipping (Outdated)
|
|
|
|
Author: Boxiang Wang, Haichen Huang, Yongbin Li
|
|
|
|
**Prerequisite**
|
|
- [Define Your Configuration](../basics/define_your_config.md)
|
|
- [Use Engine and Trainer in Training](../basics/engine_trainer.md)
|
|
|
|
**Example Code**
|
|
- [ColossalAI-Examples Gradient Clipping](https://github.com/hpcaitech/ColossalAI-Examples/tree/main/features/gradient_clipping)
|
|
|
|
**Related Paper**
|
|
- [On the difficulty of training Recurrent Neural Networks](https://arxiv.org/abs/1211.5063)
|
|
|
|
## Introduction
|
|
|
|
In order to speed up training process and seek global optimum for better performance, more and more learning
|
|
rate schedulers have been proposed. People turn to control learning rate to adjust descent pace during training,
|
|
which makes gradient vector better to be uniformed in every step. In that case, the descent pace can be
|
|
controlled as expected. As a result, gradient clipping, a technique which can normalize the gradient vector
|
|
to circumscribe it in a uniformed length, becomes indispensable for those who desire their better
|
|
performance of their models.
|
|
|
|
You do not have to worry about implementing gradient clipping when using Colossal-AI, we support gradient
|
|
clipping in a powerful and convenient way. All you need is just an additional command in your configuration
|
|
file.
|
|
|
|
## Why you should use gradient clipping provided by Colossal-AI
|
|
|
|
The reason of why we do not recommend users to write gradient clipping by themselves is that naive gradient clipping
|
|
may fail when applying tensor parallelism, pipeline parallelism or MoE.
|
|
|
|
According to the illustration below, each GPU only owns a portion of parameters of the weight in a linear layer.
|
|
To get correct norm of gradient vector of the weight of the linear layer, the norm of every gradient vector in each GPU
|
|
should be summed together.
|
|
More complicated thing is that the distribution of bias is different from the distribution of the weight.
|
|
The communication group is different in the sum operation.
|
|
|
|
(PS: This situation is an old version of 2D parallelism, the implementation in the code is not the same.
|
|
But it is a good example about the difficulty to unify all communication in gradient clipping.)
|
|
|
|
<figure style={{textAlign: "center"}}>
|
|
<img src="https://s2.loli.net/2022/01/28/KXiJPHt3Dum82cA.png"/>
|
|
<figcaption>Layout of parameters</figcaption>
|
|
</figure>
|
|
|
|
Do not worry about it, since Colossal-AI have handled it for you.
|
|
|
|
### Usage
|
|
To use gradient clipping, you can just simply add gradient clipping norm in your configuration file.
|
|
```python
|
|
clip_grad_norm = 1.0
|
|
```
|
|
|
|
### Hands-On Practice
|
|
|
|
We provide a [runnable example](https://github.com/hpcaitech/ColossalAI-Examples/tree/main/features/gradient_clipping)
|
|
to demonstrate gradient clipping. In this example, we set the gradient clipping vector norm to be 1.0. You can run the script using this command:
|
|
|
|
```shell
|
|
python -m torch.distributed.launch --nproc_per_node 1 --master_addr localhost --master_port 29500 train_with_engine.py
|
|
```
|
|
|
|
<!-- doc-test-command: torchrun --standalone --nproc_per_node=1 gradient_clipping.py -->
|