Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[feat] FP8 training

Ouverte
  • Quelque chose ne va pas ?
#63 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
8/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
python, pytorch
Domaine
ai-infra-agents

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement need update

🧐 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:

  1. Matmul Operations: Implement FP8-compatible matrix multiplication using Transformer Engine or Triton kernels.
  2. 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.
  3. Validation:
    • Compare loss curves and convergence behavior between FP8 and BF16 to ensure model stability and performance.

🔄 Alternatives Considered

  1. Continue with BF16/FP16 Precision:
    • Pros: Stable and widely supported.
    • Cons: Misses throughput and memory benefits of FP8.
  2. Partial FP8 Integration:
    • Pros: Focuses on high-impact components like matrix multiplications.
    • Cons: Could complicate debugging due to mixed precision across components.
  3. FlexAttention:
    • Pros: Potentially better support for FP8.
    • Cons: May require more development and testing for integration. May be slower than FlashAttention 3.

📈 Potential Benefits

  1. Increased Throughput: FP8 training has demonstrated up to 1.5x speedup compared to BF16 on NVIDIA H100 GPUs.
  2. Enhanced Efficiency: Reducing memory overhead enables larger batch sizes and improves GPU utilization.
  3. Scalability: Lower precision facilitates training on larger clusters without hitting memory limits.
  4. Comparable Convergence: Loss curves for FP8 have been shown to closely track those for BF16, ensuring minimal compromise in training stability.

📝 Additional Context

  1. 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.
  2. FlashAttention 3 Insights:
  3. Known Challenges:
    • Managing FP8 weight storage and quantization scaling.
    • Addressing pipeline latency issues in FP8 operations.
    • Ensuring alignment between different FP8-compatible components.
Langage dominant
Python
Étoiles
337
Forks
52
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ServiceNow/Fast-LLM

Toutes les issues de ServiceNow/Fast-LLM

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.