← Latest papers
📊 statistics

When LLMs get significantly worse: A statistical approach to detect model degradations

This article proposes a statistically grounded hypothesis testing framework based on the McNemar test to reliably detect subtle model degradations caused by numerical errors arising from optimization processes, distinguish them from benign evaluation noise, and thereby control the false positive rate.

Original authors: Jonas Kübler, Kailash Budhathoki, Matthäus Kleindessner, Xiong Zhou, Junming Yin, Ashish Khetan, George Karypis

Published 2026-05-07
📖 5 min read🧠 Deep dive

Original authors: Jonas Kübler, Kailash Budhathoki, Matthäus Kleindessner, Xiong Zhou, Junming Yin, Ashish Khetan, George Karypis

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have two identical twins, Model A (the original) and Model B (the optimized version). You want to know whether Model B is just as good as Model A or whether it has secretly become a little "dumber" to save money and run faster.

The paper argues that simply comparing the average scores of both twins in a test is like trying to hear a whisper in a hurricane. Since modern computers are inherently imperfect (due to tiny mathematical errors in how they handle numbers), even a perfect optimization can cause Model B to give a slightly different answer to exactly the same question as Model A. This creates "noise" that makes it difficult to distinguish whether a performance drop is real or just random static.

Here is the paper's solution, broken down into simple concepts:

1. The "Side-by-Side" Detective (McNemar's Test)

Most people compare models by saying: "Model A got 50% right, and Model B got 49% right. Is that a big problem?" The paper says no. That is like comparing two coin flips on different days.

Instead, the authors argue that you must look at the same question for both models at the same time.

  • The Analogy: Imagine a courtroom where you are evaluating a specific witness. You do not ask: "Did the witness usually tell the truth?" You ask: "Did the witness lie on this specific day?"
  • The Method: You examine each individual question.
    • Did Model A get it right and Model B wrong? (A "degradation")
    • Did Model A get it wrong and Model B right? (An "improvement")
    • Did both get it right or both get it wrong? (Ignore these; they do not help us decide).

The paper uses a statistical tool called the McNemar's Test (a classic method from 1947) to count only the disagreements. If Model B fails significantly more often than Model A on the exact same questions, then Model B is truly degraded. If the failures are just random noise, the test will tell you to "keep calm."

2. The "Noise" versus the "Signal"

The paper points out a funny problem: Even if you change nothing about the model (simply running it on a different computer or software version), the answers can wobble slightly back and forth due to how computers process mathematics.

  • The Metaphor: Think of a scale that is slightly wobbly. If you place a 1-kg weight on it, it might show 1.01 kg one time and 0.99 kg the next. You cannot say the weight has changed; the scale is just wobbly.
  • The Insight: The authors show that you get confused if you treat these "wobbly" wobbles as independent errors. However, if you look at the pattern of who wins and who loses on the same question, the wobbling cancels out, and the real signal (actual degradation) emerges clearly.

3. The "Three-Alarm" System (Aggregating Tests)

If you test a model on many different topics (math, history, programming, etc.), how do you decide whether the model is bad overall? The paper suggests three ways to combine the results, like three different security guards:

  1. The "Pool" Guard: Adds up all errors from every topic. Good if the model is slightly bad at everything.
  2. The "Max-Drop" Guard: Looks only for the single worst topic. Good if the model is great at everything but terrible at one specific thing (like a math genius who cannot write properly).
  3. The "Fisher" Guard: A balanced mix that mathematically combines the evidence from all topics.

The paper suggests using all three. If any one of them sounds the alarm, you know the model has likely been degraded.

4. Cutting the Fat (Reducing Dataset Size)

The paper discovered that many questions in these large tests are "too easy" or "too hard."

  • The Easy Ones: Both models get them right every time.
  • The Hard Ones: Both models get them wrong every time.
  • The "Flip" Zone: These are the tricky questions where the models are sometimes right and sometimes wrong.

The authors realized that to determine whether a model has become worse, you only need to test the questions in the "Flip Zone." The easy and hard ones are just noise. By removing the questions that never change, they could halve the size of the test dataset and still detect degradation. It is like a doctor checking only the vital signs that actually fluctuate, rather than measuring a patient's shoe size.

5. The Results: Catching Tiny Drops

The authors tested this on real Large Language Models (LLMs).

  • They found that their method could reliably detect an accuracy drop of just 0.3%.
  • They proved that some "optimizations" (such as changing hardware or using certain mathematical shortcuts) were actually safe (lossless), even though the raw numbers looked slightly different.
  • They also discovered cases where models became significantly worse (such as when using very aggressive compression), which older, simpler methods had missed because they were distracted by statistical noise.

In summary: The paper offers a rigorous, statistical "truth detector" that prevents us from panicking over random computer errors and helps us recognize when an AI model has actually lost its sharpness. It tells us to stop looking at the average score and start looking at the specific battles where the models disagree.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →