[Tech Report] USP: A Unified Sequence Parallelism Approach for Long Context Generative AI
This repo provides a sequence parallel approach that synergizes the strengths of two popular distributed attentions, i.e. DeepSpeed-Ulysses-Attention and Ring-Attention, delivering a more general and stronger versatility and better performance. The project is built on zhuzilin/ring-flash-attention and refers to the DeepSpeed-Ulysses.
USP has been applied in NVIDIA/TransformerEngine AttnFuncWithCPAndKVP2P
. You can use it in API attn_forward_func_with_cp
.
Ulysses is sensitive to the number of attention heads. The parallelism degree in Ulysses cannot exceed the number of heads. Consequently, it is not suitable for GQA (Grouped Query Attention) and MQA (Multi-Query Attention) scenarios. For instance, Ulysses does not operate effectively with a single head. In addition, since Tensor Parallelism also requires division across the head number dimension, achieving compatibility between Ulysses and TP can be challenging.
Ring-Attention is ineffient than Ulysses in computation and communication. Ring-Attention segments the Query, Key, and Value (QKV) into smaller blocks, which can lead to a decrease in efficiency when using FlashAttention. Even with the communication and computation processes fully overlapped, the total execution time lags behind that of Ulysses. Furthermore, Ring-Attention utilizes asynchronous peer-to-peer communication, which not only has a lower bandwidth utilization compared to collective communication methods but also poses the risk of potential communication deadlocks in large-scale deployments.
LongContextAttention
is a unified sequence parallel , also known as hybrid sequence parallel ,that hybrid DeepSpeed-Ulysses-Attention and Ring-Attention therefore addressing the limitations of both methods.
Please refer to test/test_hybrid_qkvpacked_attn.py and test/test_hybrid_attn.py for usage.
In short, we take the zigzag
ring attention implementation as an example:
set_seq_parallel_pg
to set the process groupzigzag_extract_local
. We need reorder the input tokens or input tensors for load balance ring attention.LongContextAttention(ring_impl_type="zigzag")
as a drop-in replacement for Attention implementation.Option 1: pip install from pypi.
pip install yunchang
(flash_attn >= 2.6.0)
pip install yunchang==0.2
(flash_attn < 2.6.0)
Option 2: build from local.
pip install .
Install for AMD GPU: install_amd.md
The loss curves for Data Parallel (DP) and Unified Sequence Parallel (ulysses=2+ring=2) are closely aligned, as illustrated in the figure. This alignment confirms the accuracy of the unified sequence parallel.
When utilizing load-balance Ring Attention with a causal mask, it is essential to reorder the Query tensors using the EXTRACT_FUNC_DICT function.
In Megatron-LM, you can reorder the input tokens before feeding them into the model and apply the same reordering to the RoPE parameters. For detailed instructions, please refer to our paper.
For an example implementation, you can check out this PR, which integrates USP into a BAAI's Megatron-LM framework.
We analyze the impact of introducing Sequnce Parallelism to Data/ZeRO/Tensor/Pipeline Parallelism in a technique report, which can be found at here.
Some best practices are listed here:
We suggest using Unified-SP in place of SP-Ring and SP-Ulysses, as it encompasses the capabilities of both while offering additional benefits.
DP (data parallelism) vs SP: We suggest prioritizing the use of DP over SP if possible. Only when the batch size (bs) is insufficient for partitioning should one consider whether to employ SP
Utilizing SP, it should always be used in conjunction wit ZeRO-1/2.
Unified-SP has lower communication cost than Tensor Parallel with megatron-lm sequence parallelism (TP-sp)! You can use Unified-SP to replace TP for better speed. However, now switching TP (tensor parallelism) to SP+ZeRO2 cannot increase the sequence length in training. SP+ZeRO3 can train a similar sequence length as TP-sp. We suggest that SP may have an advantage over TP when employing GQA in terms of communication cost, as GQA can reduce the communication cost of SP without affecting TP.
Setting a higher parallel degree of SP parallelism is possible, which may need to set a large ring degree when the head number is limited, to train a long sequence across a greater number of computational devices. But TP could not be set a high parallel.
torchrun --nproc_per_node 8 test/test_hybrid_qkvpacked_attn.py
bash ./scripts/run_qkvpack_compare.sh
On an 8xA100 NVLink machine, the benchmark results are as follows:
On an 8xL20 PCIe machine and a 4xA100 PCIe machine, the benchmark results are as follows:
Some Conclusions:
If the head number is enough, Ulysses outperforms Ring-Attention. The All-to-All communication of Ulysses is highly efficient within a single machine, with a very low overhead ratio. In contrast, Ring splits computation and communication, which increases the overall of computation time, and even with complete overlap, it is slower than Ulysses.
QKV packed (LongContextAttentionQKVPacked
) is better than the QKV no packed (LongContextAttention
) version, with the difference becoming more pronounced as the sequence length decreases. MAQ and GQA can only use the no packed version.
Among the variants of the Ring-Attention implementation, zigzag
and stripe
perform better than basic
. Typically, zigzag is slightly better than stripe, but as the sequence length increases, the difference between zigzag and stripe becomes less noticeable. It is worth noting that both zigzag and stripe have specific layout requirements for the sequence dimension.
Hybrid parallelism works well to heterogeneous network devices. For example, on an 8-GPU L20 setup, the optimal performance is achieved when ulysess_degree is set to 2 and ring_degree is set to 4.
I am honored that this repository has contributed to the following projects:
@article{fang2024unified,
title={USP: A Unified Sequence Parallelism Approach for Long Context Generative AI},
author={Fang, Jiarui and Zhao, Shangchun},
journal={arXiv preprint arXiv:2405.07719},
year={2024}
}