Opt.Gear-QAT: Preserving On-Device Performance with QAT
Introducing the Quantization-Aware Training recipe for Opt.Gear-1B, combining Hessian-based scale initialization with LSQ.
🤗 HUGGING FACE 🏠 OptAI ✉️ CONTACT
Opt.Gear is a foundation model developed in-house for on-device environments. The family includes the general-purpose language models Opt.Gear-1B and Opt.Gear-270M, and an ultra-lightweight model with approximately 1M parameters for microcontrollers.
This is the second article in the Opt.Gear series. Following Part 1: Introducing Opt.Gear , which covers the model architecture and training recipe, this article discusses quantization-aware training (QAT). The next article introduces Opt.Gear-1M , an ultra-small model for microcontrollers.
Making a small model is not enough for deployment on real devices. In addition to parameter count, weight memory, memory bandwidth, compute precision, and the kernels supported by the accelerator determine inference performance.
The question is how much of the original performance can be retained when the model is reduced to 4 bits .
For Opt.Gear-1B, we applied Quantization-Aware Training (QAT) so that the trained model adapts directly to the INT4 grid used for deployment. These weights also minimize performance loss when subsequently used with other INT4 PTQ algorithms.
Key points
- Group size 32 with symmetric INT4 weight quantization
- 16-bit activations in a W4A16 configuration
- Calibration activations for Hessian-based scale initialization
- Learned Step Size Quantization(LSQ) for joint optimization of weights and scales
- Short QAT adaptation in just 1,000 training steps
Quantization parameters of Opt.Gear-1B
Opt.Gear-1B QAT uses the following final deployment conditions.
| Item | Configuration |
|---|---|
| Weight precision | INT4 |
| Activation precision | INT16 |
| Quantization format | W4A16 |
| Weight quantization | Symmetric |
| Group size | 32 |
| Scale initialization | Hessian-based output reconstruction |
| Scale optimization | Learned Step Size Quantization |
| QAT length | 1,000 steps |
Group size 32 uses an independent scale for each group of 32 weights. This increases scale metadata compared with per-tensor quantization, but allows a suitable range to be assigned to each region of weights with a different distribution.
Symmetric quantization fixes the zero-point at 0 and represents positive and negative values around the scale. This simplifies quantization operations and deployment kernels, but without a suitable scale, the limited INT4 grid may be used inefficiently.
Opt.Gear-1B therefore uses layer output distortion measured with calibration activations instead of simple max-based scale initialization.
Opt.Gear-1B QAT Pipeline
1. Quantization scale is important
Uniform weight quantization projects real-valued weights onto a limited integer grid:
Here, Δ is the quantization scale, or step size. Since INT4 has very few representable integer values, choosing the scale is critical:
- If the scale is too large, clipping decreases but quantization intervals become coarse.
- If the scale is too small, small weights can be represented precisely but large weights are clipped.
- Expanding the range to accommodate a few outliers concentrates most weights into a small number of quantization bins.
2. Hessian-based scale initialize
Simple PTQ methods such as RTN generally determine scales from the maximum absolute weight or weight range. This is straightforward to implement, but assumes that every weight perturbation has the same effect on the model output . In practice, even weight errors of equal magnitude have a greater impact on layer outputs when they occur along directions frequently traversed by input activations.
For Opt.Gear-1B, we estimated the sensitivity of each layer using calibration inputs and determined the initial INT4 scale for each group with the following output reconstruction objective:
This approach starts from GPTQ and its second-order output reconstruction perspective, but does not apply the full GPTQ algorithm unchanged. Opt.Gear uses this objective to find the initial group-wise scales for QAT, then jointly optimizes weights and scales against the overall training objective.
3. LSQ-based QAT
Hessian-based initialization effectively reduces initial output distortion in each layer. However, a layer-wise reconstruction objective does not directly optimize the performance of the entire language model. Small errors can accumulate across layers; some barely affect token prediction, while others substantially change the final logits.
After finding a good starting point with Hessian initialization, QAT with the full language modeling objective is therefore necessary. Opt.Gear-1B initializes scales from the Hessian-based values, then uses Learned Step Size Quantization(LSQ) to make the scales learnable parameters.
The forward pass simulates the same symmetric INT4 grid used for deployment:
round cannot be differentiated directly, so the backward pass approximates gradients with a Straight-Through Estimator (STE). LSQ propagates task-loss gradients to the step size Δ as well as the weights. Scale gradients are normalized by the number of elements in each group and the number of positive quantization levels. This prevents scale updates from overwhelming weight updates while allowing group-wise step sizes to be optimized jointly with model parameters.
Two adaptations take place together during QAT:
- Weights move toward distributions that are easier to represent on the INT4 grid.
- Group-wise scales adjust to clipping ranges and resolutions suited to the task loss.
Hessian-based initialization and LSQ play different roles:
| Stage | Role |
|---|---|
| Hessian-based initialization | Select scales with low layer output distortion at the start of QAT |
| LSQ-based QAT | Optimize weights and scales for the full language modeling loss |
| Maintain the same W4A16 grid | Prevent quantization mismatch between training and final export |
Performance of QAT
We compared the Base, QAT, and PTQ results of Opt.Gear-1B and Gemma3-1B on six shared English and Korean benchmarks. RTN, AWQ, and GPTQ results come from requantizing the master weights of the QAT-trained checkpoints with each PTQ method. The QAT rows evaluate the final QAT quantizer, including the learned scales.
| Method | MMLU | HellaSwag | WinoGrande | KMMLU | KoBEST | HAERAE | Avg. | Δ |
|---|---|---|---|---|---|---|---|---|
| Opt.Gear-1B | ||||||||
| Base | 43.2 | 56.0 | 58.2 | 36.0 | 60.3 | 44.2 | 49.7 | – |
| QAT | 41.3 | 54.0 | 58.3 | 35.0 | 60.4 | 42.7 | 48.6 | -1.0 |
| RTN | 39.8 | 53.9 | 56.9 | 33.8 | 59.8 | 39.9 | 47.4 | -2.3 |
| AWQ | 39.5 | 52.6 | 56.5 | 32.7 | 59.6 | 38.2 | 46.5 | -3.1 |
| GPTQ | 39.6 | 53.5 | 57.1 | 34.4 | 59.6 | 41.0 | 47.5 | -2.1 |
| Gemma3-1B | ||||||||
| Base | 39.8 | 60.0 | 58.7 | 30.7 | 59.5 | 35.3 | 47.3 | – |
| QAT | 35.8 | 51.4 | 55.0 | 26.9 | 56.2 | 31.2 | 42.8 | -4.6 |
| RTN | 32.5 | 48.5 | 53.8 | 21.2 | 55.1 | 23.6 | 39.1 | -8.2 |
| AWQ | 34.3 | 50.5 | 53.7 | 23.3 | 56.4 | 29.7 | 41.3 | -6.0 |
| GPTQ | 34.9 | 49.6 | 54.9 | 23.3 | 55.1 | 27.1 | 40.8 | -6.5 |
Avg. is the unweighted mean of the six benchmark scores; Δ is the difference from each model’s Base average.* Bold values indicate the highest quantized result for each model.
* See the technical report for PTQ results for Llama3.2-1B, Qwen3-1.7B, and EXAONE4-1B.
The six-benchmark average for Opt.Gear-1B decreased from Base 49.7 to QAT 48.6, a reduction of approximately 1.0 point . The average decline was approximately 1.3 points across the three English metrics and 0.8 points across the three Korean metrics. Crucially, the actual symmetric W4A16 deployment conditions with group size 32 were applied unchanged , yet just 1,000-step QAT preserved both English and Korean performance.
Under the same conditions, Gemma3-1B decreased from a Base average of 47.3 to a QAT average of 42.8, a reduction of approximately 4.6 points . Differences in architecture, pretraining, and QAT recipes mean that this gap cannot be attributed to a single factor. The results nevertheless suggest that Hessian initialization and LSQ gave Opt.Gear-1B a stable starting point and convergence path even with short QAT training.
Quantization stability
Opt.Gear-1B performs best with its learned scales, but the QAT-trained weights themselves also remain relatively stable under other INT4 quantizers.
| Model | Quantizer | Avg | Change from QAT |
|---|---|---|---|
| Opt.Gear-1B-QAT | |||
| Learned QAT scale | 48.6 | – | |
| RTN | 47.4 | -1.3 | |
| AWQ | 46.5 | -2.1 | |
| GPTQ | 47.5 | -1.1 | |
| Gemma3-1B-QAT | |||
| Learned QAT scale | 42.8 | – | |
| RTN | 39.1 | -3.6 | |
| AWQ | 41.3 | -1.4 | |
| GPTQ | 40.8 | -1.9 | |
Gemma3-1B also underwent PTQ from its QAT checkpoint, but switching to RTN reduced its average by 3.6 points. Under the same RTN requantization conditions, Opt.Gear-1B lost only 1.3 points on average, demonstrating greater stability.
The Opt.Gear-1B QAT checkpoint is not just a set of learned scale parameters: the weights themselves have been adjusted to be quantization-friendly . Performance remains stable with different INT4 quantizers, providing flexibility in the choice of quantization tools for deployment pipelines.
Conclusion
Opt.Gear-1B QAT was designed around three principles:
- Rather than looking only at weight ranges, measure the impact on outputs using calibration activations .
- Hessian-based output reconstruction provides a good group-wise INT4 scale from which to start training.
- Learned Step Size Quantization jointly optimizes weights and scales for the final task objective.
Using the same symmetric W4A16 grid with group size 32 throughout initialization, QAT, and final export prevents the learned quantization structure from being lost during deployment conversion. After just 1,000-step QAT, Opt.Gear-1B differed from Base by only about 1.0 point in the unweighted average across six English and Korean benchmarks.
The next article introduces Opt.Gear-1M, which extends this design philosophy to microcontroller scale.
Citation
@misc{optgear2026,
title = {{Opt-Gear} Technical Report},
author = {{OptAI Gear Team}},
year = {2026},
url = {https://huggingface.co/OptGear}
}
Correspondence: contact@opt-ai.kr · Hugging Face: huggingface.co/OptAI