[feat] FP8 training
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 8/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Ambito
- ai-infra-agents
Direzione di ricerca
This is an open design question spanning matmul kernels and attention integration, with no linked pull request and no assignee. The payload names no concrete file or test to start from, so a newcomer would first need to read the training stack and the FlashAttention 3 FP8 discussion it links. Done would mean a recorded decision on FP8 attention plus a BF16-versus-FP8 loss comparison, which is maintainer-level scope.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
🧐 Problem Description
FP8 training can significantly improve training throughput by reducing memory requirements and improving computational efficiency. However, challenges remain in integrating FP8 across all components of the training stack, such as FlashAttention, while maintaining model performance and stability. For example, the FP8 implementation in FlashAttention 3 raises questions about quantization accuracy and latency between operations.
💡 Proposed Solution
Introduce FP8 training in Fast-LLM with the following steps:
- Matmul Operations: Implement FP8-compatible matrix multiplication using Transformer Engine or Triton kernels.
- FlashAttention Compatibility:
- Evaluate the feasibility of integrating FlashAttention 3, which supports FP8.
- Address concerns about quantization accuracy and potential pipeline latency.
- Explore alternatives like FlexAttention if FlashAttention 3 proves unsuitable.
- Validation:
- Compare loss curves and convergence behavior between FP8 and BF16 to ensure model stability and performance.
🔄 Alternatives Considered
- Continue with BF16/FP16 Precision:
- Pros: Stable and widely supported.
- Cons: Misses throughput and memory benefits of FP8.
- Partial FP8 Integration:
- Pros: Focuses on high-impact components like matrix multiplications.
- Cons: Could complicate debugging due to mixed precision across components.
- FlexAttention:
- Pros: Potentially better support for FP8.
- Cons: May require more development and testing for integration. May be slower than FlashAttention 3.
📈 Potential Benefits
- Increased Throughput: FP8 training has demonstrated up to 1.5x speedup compared to BF16 on NVIDIA H100 GPUs.
- Enhanced Efficiency: Reducing memory overhead enables larger batch sizes and improves GPU utilization.
- Scalability: Lower precision facilitates training on larger clusters without hitting memory limits.
- Comparable Convergence: Loss curves for FP8 have been shown to closely track those for BF16, ensuring minimal compromise in training stability.
📝 Additional Context
- Key Findings from Databricks:
- FP8 training achieves ~1.5x throughput improvement.
- Integrated with PyTorch FSDP and activation checkpointing for memory efficiency.
- Loss curves for FP8 closely match BF16 during training.
- Databricks Blog: Turbocharged Training with FP8.
- FlashAttention 3 Insights:
- FlashAttention 3 supports FP8 but has open questions about latency and accuracy.
- FlashAttention 3 Issue: FP8 Concerns.
- Known Challenges:
- Managing FP8 weight storage and quantization scaling.
- Addressing pipeline latency issues in FP8 operations.
- Ensuring alignment between different FP8-compatible components.
- Lingua principale
- Python
- Stelle
- 337
- Fork
- 52
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ServiceNow/Fast-LLM
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
ServiceNow/Fast-LLM#556 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 30/100
ServiceNow/Fast-LLM#538 ·
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
ServiceNow/Fast-LLM#533 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
ServiceNow/Fast-LLM#510 · 1 commento ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
ServiceNow/Fast-LLM#507 ·
Tutte le issue di ServiceNow/Fast-LLM
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
-
Validate finite output clamping limits in StepPredictor.prepare_clamping_params to prevent silent NaN/Inf propagationForse già presa @muskan-creates352 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
mllam/neural-lam#848 ·
I maintainer di solito rispondono entro 2 giorni
-
infra
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
fab-geocommuns/RNB-coeur#1166 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
deepspeedai/DeepSpeed#8951 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
aws/context-ontology-accelerator#343 ·
I maintainer di solito rispondono entro 1 giorno