Skip to content
#software testing Open access

The quant_eval Public Corpus: Behavioral Measurement of Quantization Degradation—Precision, Scale, and Substrate Effects

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research) · 2 references

Abstract

This paper presents the quant_eval public corpus: a paired behavioral evaluation of full-weight and quantized large language models across eight agent-relevant task families, published as eight open datasets with per-case evidence, paired statistical tests, and a verification chain a reader can check rather than trust. Quantization documentation reports memory footprint and perplexity. It does not report whether a quantized model still emits valid structured output, dispatches the right tool with the right arguments, carries state across turns, or completes a multi-step plan. This corpus measures those behaviors directly, per capability, against an identical full-weight baseline on byte-identical fixtures.

Method

Each run executes a full-weight lane and a quantized lane over the same 1,600 cases — 200 per family — with correctness defined by a deterministic first-fit oracle rather than a reference model. A family's pass rate is the fraction of cases satisfying every gating signal in that family's published conjunction. Paired differences are tested with McNemar's test, with a cluster adjustment published alongside the unadjusted value for the one family carrying semantic duplicates. A named taxonomy of harness artifacts is neutralized centrally so that output-format drift is not scored as capability loss. The evaluation methodology is quant_eval v7.22, a breaking redesign of the v7.21 framework described in the first quant_eval paper. Results from the two versions are not comparable. CORPUS Six runs across four base models, six model–precision pairs, and three quantization schemes. Mistral-Nemo-Instruct-2407 was evaluated at Q4_K_M, Q5_K_M, and Q8_0 against a shared F16 baseline, isolating precision. Qwen2.5-7B-Instruct, Qwen2.5-14B-Instruct-1M, and Qwen2.5-32B-Instruct were each evaluated at Q4_K_M, alongside Mistral-Nemo, isolating scale. 19,200 per-case rows in total.

Findings

The Mistral-Nemo full-weight baseline, executed three times across three runs, produced byte-identical outcomes on all 1,600 cases, establishing that the harness contributes no measurement noise on fixed hardware. Quantization cost is capability-specific and abrupt rather than gradual. At Q4_K_M, five of eight Mistral-Nemo families degrade significantly, two do not move, and one improves; at Q5_K_M and Q8_0, no family moves significantly in either direction. A single aggregate score would have averaged these outcomes into a number describing none of them. Quantization cost is model-dependent: at the same precision, Qwen2.5-7B loses two families where Mistral-Nemo loses five. The result cannot be transferred from one model to another; it has to be measured per model. On matched hardware, quantization delivered 1.71× to 2.70× faster wall time. Two runs showing apparent slowdowns are hardware-downgrade artifacts, not quantization effects, and are recorded as such in the published data. SCOPE AND

Limitations

The Qwen2.5-14B and Qwen2.5-32B runs were served through a remote inference endpoint originally deployed for a separate agent product. That endpoint declared no seed argument and fixed its sampling values and accelerator assignments at the application level, so those two runs are valid measurements under recorded conditions but are not bit-reproducible, and their wall-time ratios are not quantization effects. This is a property of that deployment, not of the hosting platform. Decoding temperature follows each publisher's model card and differs between the two model lineages, which confounds cross-model comparison. The paper states eight limitations explicitly, and names which published field lets a reader filter on each. The paper also accounts for what the measurement costs: under seven dollars of electricity and metered compute for the entire study, on a single consumer GPU, with capital stated separately. DATA AVAILABILITY All eight datasets are deposited under CC BY 4.0 and cited in the paper by concept DOI, with the corpus record at 10.5281/zenodo.22009419. Paired degradation statistics and family pass rates are recomputable in full from the published per-case rows; the paper states which datasets are recomputable and which are traceable through digests only. The derivation tooling is published under Apache-2.0. quant_eval itself is proprietary software of PBH Applied Systems, LLC and is not published.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.