Papers › A Comprehensive Evaluation of Quantization Strategies for Large Language Models

A Comprehensive Evaluation of Quantization Strategies for Large Language Models

26 Feb 2024arXiv:2402.16775archive 2025-07-28

Renren Jin, Jiangcun Du, Wuwei Huang, Wei Liu, Jian Luan, Bin Wang, Deyi Xiong

Increasing the number of parameters in large language models (LLMs) usually improves performance in downstream tasks but raises compute and memory costs, making deployment difficult in resource-limited settings. Quantization techniques, which reduce the bits needed for model weights or activations with minimal performance loss, have become popular due to the rise of LLMs. However, most quantization studies use pre-trained LLMs, and the impact of quantization on instruction-tuned LLMs and the relationship between perplexity and benchmark performance of quantized LLMs are not well understood. Evaluation of quantized LLMs is often limited to language modeling and a few classification tasks, leaving their performance on other benchmarks unclear. To address these gaps, we propose a structured evaluation framework consisting of three critical dimensions: (1) knowledge \& capacity, (2) alignment, and (3) efficiency, and conduct extensive experiments across ten diverse benchmarks. Our experimental results indicate that LLMs with 4-bit quantization can retain performance comparable to their non-quantized counterparts, and perplexity can serve as a proxy metric for quantized LLMs on most benchmarks. Furthermore, quantized LLMs with larger parameter scales can outperform smaller LLMs. Despite the memory savings achieved through quantization, it can also slow down the inference speed of LLMs. Consequently, substantial engineering efforts and hardware support are imperative to achieve a balanced optimization of decoding speed and memory consumption in the context of quantized LLMs.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2402.16775")

Code

Syntology Ran 8 of 11 code samples harvested from 1 repository linked to this paper; 3 have no recorded run. Of those that ran: 1 ran · violated contract; 2 ran · our draft was wrong; 5 ran with no contract checked.

By repository: official repository: 11 samples from 1 repository, 8 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested; 8 ran; 0 honoured the contract we drafted; 3 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · violated contract
2ran · our draft was wrong
5ran
3unverified

Licence: 11 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from cordercorder/quant_eval. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

mean cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/metrics.py official repository ran · violated contract fingerprinted no licence file found · pointer only · 0928f497e20fb443 · report
general_detokenize cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/utils.py official repository ran fingerprinted no licence file found · pointer only · 0662e7a6743f488b · report
get_result cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/models/gpt3.py official repository ran no licence file found · pointer only · d253589f2c78dad0 · report
group cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/utils.py official repository ran no licence file found · pointer only · 359c35fdcd7a0ee5 · report
hash_args cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/base.py official repository ran · our draft was wrong fingerprinted no licence file found · pointer only · ea06eaae4fc1eaf0 · report
pop_stddev cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/metrics.py official repository ran fingerprinted no licence file found · pointer only · 518b2201c66c2ad3 · report
sample_stddev cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/metrics.py official repository ran · our draft was wrong fingerprinted no licence file found · pointer only · d40f0123e8a8f5c0 · report
simple_parse_args_string cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/utils.py official repository ran fingerprinted no licence file found · pointer only · cd999ad59caf84a7 · report
load_models_tokenizer cordercorder/quant_eval/benchmarks/alpaca_eval/evaluate_llm_int8_quant_qwen_chat.py official repository unverified no licence file found · pointer only · 2251707ba84890b2 · report
make_table cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/evaluator.py official repository unverified no licence file found · pointer only · 9d95c14130837ee4 · report
stop_sequences_criteria cordercorder/quant_eval/quant/SpQR/lm-evaluation-harness/lm_eval/models/huggingface.py official repository unverified no licence file found · pointer only · 069ffbe9aadaa2ae · report

Tasks

Language ModelingLanguage ModellingQuantization

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

SPEED

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections