AIToday
Large Language ModelsAI Coding AssistantsGIGAZINE AIPublished: Oct 21, 2026, 01:00 JST

Parsimony benchmark scores AI models on code bloat

Send on LINE
Parsimony benchmark scores AI models on code bloat

3 Key Points

  1. What happened

    Parsimony analyzes AI fixes from existing benchmarks and counts added versus deleted "coding units" — syntax elements like branches and variable names. Claude Opus 5.5(high) added about 1.1× the code of other models; GPT-6.1 Sol(high)・Codex, about 0.7×.

  2. Why it matters

    High problem-solving scores do not guarantee lean code, so teams judging AI coding tools may need to weigh maintainability alongside accuracy, though the developer notes that less code does not always mean higher quality.

WHO IT HITSSoftware engineers and engineering managers choosing AI coding assistants are the main audience, since the benchmark compares how much code each model adds when fixing the same problem. Maintainers of long-lived codebases may find the added-code measure more relevant than raw solve rates.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The benchmark arrives at a moment when AI coding tools are commonly judged by whether they solve a problem and what that costs. Parsimony adds a third axis: how much code the model writes to get there. Its unit of measurement is designed to resist gaming — counting conditional branches, function calls, variable names and numbers rather than lines, and excluding line breaks, whitespace and comments so that compressing code onto fewer lines does not flatter the result. Test code, documentation and automatically generated files are left out of the measurement.

The published comparison places the Intelligence Index, calculated by the AI evaluation site Artificial Analysis, on the vertical axis and added code relative to other models on the horizontal axis. The spread suggests that a higher index does not by itself predict leaner fixes. The developer cautions that this cuts both ways: shorter code can be harder to follow, and volume alone says nothing definitive about readability or design.

Because the source code and measurement data are public on GitHub, the results can be reproduced, and the developer is soliciting fix data for additional models and feedback on the evaluation method — a sign the comparison set may expand beyond the models shown so far.

FAQ
How does Parsimony measure code size?
It counts "coding units" — syntax elements such as conditional branches, function calls, variable names and numbers — rather than lines. Line breaks, whitespace and comments are excluded, so cramming multi-line code onto one line does not improve the score.
Can a model score a negative value?
Yes. Because deleted units are subtracted from added units, a fix that simplifies existing code can produce a negative number; replacing a loop with Python's built-in sum, for example, came to a 10-unit reduction.
Is less code always better?
No. According to the developer, code that is too short can be hard to understand, and code volume alone cannot judge readability or design quality.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleG7 digital ministers take up frontier AI security