logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·31.10.26
← Back to news

LLMs: Intelligence vs. Cost

Original article
openteams.com|55 points|24 comments|by theanonymousone|Sep 2, 2026

LLMs: Balancing Intelligence and Expenditure

Published September 1, 2026

The website ArtificialAnalysis (AA) provides a critical service by benchmarking the cognitive capabilities of various Large Language Models (LLMs). Their primary metric, the Intelligence Index, is derived from the average results of a curated set of benchmarks. While this serves as a helpful "rough estimate" of a model's overall smarts, AA also tracks the financial cost of executing these benchmarks.

Because the tests are standardized, these costs provide a relative proxy for what an end-user will pay. This is a vital consideration: using a "frontier" model for a trivial task is efficient a complete waste of resources.

The Flaws in the Original Visualization

Despite its utility, the plotting method used by AA is frustrating for several reasons. I believe their current approach is misleading:

IssueWhy it's problematic
Logarithmic ScalingIt masks the gargantuan price gap between budget models and premium ones, while exaggerating tiny differences between cheap models.
Official API PricingIt relies on developer-set prices, ignoring the fact that open-weights models are often significantly cheaper via third-party providers.
Local Model MispricingModels capable of running on consumer hardware are listed at datacenter rates, which no local user would actually pay.

Key Insight: To optimize costs, one should use OpenRouter to switch providers dynamically and secure the lowest possible rate.


A New Approach to Visualization

I have reconstructed these plots using AA's intelligence scores but applying a more realistic cost framework.

Understanding the Intelligence Metric

When interpreting the intelligence axis, keep these guidelines in mind:

  • ±1\pm 1±1 point: Likely imperceptible to the average user.
  • ±5\pm 5±5 points: A substantial and noticeable difference in capability.
  • Baseline: A score of 50 represents the state-of-the-art as of February 2026 (specifically Opus 4.6).

The Three-Tiered View

I created three distinct visualizations to better illustrate the landscape:

  1. High-Intelligence Tier: Focuses on the most capable (and pricey) models.
  2. Low-Cost Tier: Zooms into the "green zone" where models are extremely affordable, extending down to smartphone-capable models.
  3. The Unified View: Merges both to highlight the diminishing returns of paying for more intelligence.

High Intelligence Plot Low Cost Plot All Models Plot


Methodology and Data Adjustments

To arrive at these plots, I implemented the following changes:

  • Swapped the x-axis from logarithmic to linear (because budgets are linear).
  • Updated pricing for Kimi K3, Qwen3.8 Max, DeepSeek V4 Flash 0731, GLM-5.3, GLM-5.3-Flash, and Hy3 using OpenRouter rates (filtering for reliability and Zero Data Retention).
  • Extrapolated GLM-5.3-Flash high-reasoning scores by combining AA data with Z.ai coding benchmarks.
  • Replaced datacenter pricing with local electricity costs for models under 35 billion parameters.
  • Integrated Ornith-1.5-35B-A3B (using self-reported scores, which should be viewed with skepticism).

Calculating Local Execution Costs

For models marked with ⚡, the cost per task was determined using the following logic:

The mathematical formula for the electricity cost is roughly: Cost=(TokensTokens/sec×Power Draw (kW)×$0.2049/kWh)×1.15\text{Cost} = \left( \frac{\text{Tokens}}{\text{Tokens/sec}} \times \text{Power Draw (kW)} \times \$0.2049/\text{kWh} \right) \times 1.15Cost=(Tokens/secTokens​×Power Draw (kW)×$0.2049/kWh)×1.15

Hardware Assumptions:

  • GPU: Used an RTX 3090 (~$1,400 used).
  • Electricity: Weighted US average of \0.2049/\text{kWh}$ (May 2026).
  • Hardware Cost: Set to \0$ for machines under 64GB RAM, as these are standard gaming/workstation builds.

The Hardware Threshold

While ignoring hardware costs is fair for general-purpose PCs, it fails once you exceed 64GB of RAM.

For example, Qwen3.8-Flash requires at least a 128GB Strix Halo. While I show both the datacenter price and the local electricity cost for this model, the electricity figure is deceptive because it ignores the massive hardware premium:

  • 64GB Strix Halo: \approx \2,000$ (Useful for many tasks).
  • 128GB Strix Halo: \approx \3,600$ (Primarily only useful for high-end AI).

Author Avatar Additional context images: