Jetfire: Efficient and Accurate Transformer Pretraining with INT8 Data Flow and Per-Block Quantization

Haocheng Xi, Yuxiang Chen, Kang Zhao, Kaijun Zheng, Jianfei Chen +1 more
2/12/2026

No official code found. Best implementation: thu-ml/Jetfire-INT8Training (63 stars, last commit 2024-07-21).

Abstract

Pretraining transformers are generally time-consuming. Fully quantized training (FQT) is a promising approach to speed up pretraining. However, most FQT methods adopt a quantize-compute-dequantize procedure, which often leads to suboptimal speedup and significant performance degradation when used in transformers due to the high memory access overheads and low-precision computations. In this work, we propose Jetfire, an efficient and accurate INT8 training method specific to transformers. Our method features an INT8 data flow to optimize memory access and a per-block quantization method to maintain the accuracy of pretrained transformers. Extensive experiments demonstrate that our INT8 FQT method achieves comparable accuracy to the FP16 training baseline and outperforms the existing INT8 training works for transformers. Moreover, for a standard transformer block, our method offers an end-to-end training speedup of 1.42x and a 1.49x memory reduction compared to the FP16 baseline. Our code is open sourced at https://github.com/thu-ml/Jetfire-INT8Training.

View on arXivView PDF

Code Implementations(1)

639C, C++Jul 21, 20242 years ago

Similar Papers

Cite this paper

@article{xi2026jetfire,
  title  = {Jetfire: Efficient and Accurate Transformer Pretraining with INT8 Data Flow and Per-Block Quantization},
  author = {Haocheng Xi and Yuxiang Chen and Kang Zhao and Kaijun Zheng and Jianfei Chen and Jun Zhu},
  year   = {2026},
  eprint = {2403.12422},
  archivePrefix = {arXiv},
  url    = {https://arxiv.org/abs/2403.12422},
  journal = {ICML 2024 2024}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2403.12422.svg)](https://codeofpaper.com/paper/2403.12422)

Discussion