atlas

Research map / Architectures and efficiency / Quantization

LoTA-QAF: Lossless Ternary Adaptation for Quantization-Aware Fine-Tuning

NeurIPS 2025 · Architectures and efficiency › Quantization · approach: Ultra-low-bit LLM quantization · 0 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Proposes LoTA-QAF, a quantization-aware fine-tuning method that uses ternary adapters and a sign-based optimizer (t-SignSGD) to adjust all quantized weights in-grid and merge losslessly into GPTQ-quantized LLMs.

Problem

Fine-tuning quantized LLMs with high-precision adapters (e.g., LoRA) causes data-type mismatch at inference and accuracy loss when adapters are merged into low-bit weights, while existing lossless merges (e.g., QA-LoRA) only adjust zero factors rather than the quantized weights.

Approach

Ternary adapters A_T, B_T in {-1,0,1} form an auxiliary matrix whose thresholded ternary version is added directly to the integer quantized weights, with an offset absorbed into the zero factor, enabling lossless merging; t-SignSGD updates the ternary adapters using sign updates gated by a dynamic top-percentile gradient threshold.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Use LoTA-QAF instead of GPTQ+LoRA for 2-bit quantizationQwen 2.5 14B · MMLU (5-shot)accuracy: 42.66 -> 47.80Helped
Use LoTA-QAF instead of GPTQ+LoRA for 2-bit quantizationQwen 2.5 32B · MMLU (5-shot)accuracy: 48.46 -> 52.65Helped
Use LoTA-QAF instead of GPTQ+LoRAQuantized models across tested sizes and bit widths · MMLU (5-shot), Avg.accuracyHelped
Use LoTA-QAF instead of QA-LoRAQuantized models · Task-specific GSM8K, SQL, and ViGGOaccuracyHelped
Use LoTA-QAF instead of 16-bit-adapter LoRA after mergingLlama 3.1 8B · ViGGO inference, 4-, 3-, and 2-bitthroughput speedup: 1.9x, 1.7x, and 2.0xHelped
Use LoTA instead of LoRALlama 3.1 8B · SQL generation, 2-bitconvergence loss: 0.132 -> 0.375Hurt
Use LoTA instead of LoRALlama 3.1 8B · SQL generation, 4- and 3-bitconvergence loss difference: <0.01No clear effect
Implement ternary adapters with LoTA-QAF rather than LoRALlama 3.1 8B, 4-bit · Training across four datasetstraining time: 14.1%-25.4% more training timeHurt
Implement ternary adapters with LoTA-QAF rather than LoRALlama 3.1 8B, 4-bit · Training across four datasetspeak memory usage: 2.6%-6.3% overheadHurt
Set TA threshold ω to 48 rather than the other tested values (ablation)Llama 3.1 8B · GSM8K, 4-, 3-, and 2-bitaccuracyHelped
Use a larger ω to make quantized-weight adjustments more conservative (ablation)Llama 3.1 8B · GSM8K, 2-bitaccuracyHelped
Use a smaller ω (ablation)Llama 3.1 8B · GSM8K, 3- and 2-bitaccuracyHurt

Surprising findings

Limitations

Experimental setup

Datasets: Alpaca GSM8K SQL generation ViGGO C4

Benchmarks: MMLU GSM8K SQL generation ViGGO

Metrics: accuracy throughput (tokens/s) peak memory training time

Baselines: GPTQ+LoRA QA-LoRA GPTQ

Builds on: LoRA QA-LoRA QLoRA GPTQ AutoRound

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy