GPT‑5.

PromptCube Intermediate 2h ago 225 views 13 likes 1 min read

I've been running benchmarks on GPT‑5.6 for a couple of weeks now, and the number that matters most—cost per useful token—has genuinely dropped without much sacrifice. The model lands somewhere between GPT‑5 and GPT‑4o on raw accuracy but at about a third of GPT‑5's inference cost for large batches. That's not incremental, that's a different budget conversation.

The architecture shift is the story. They've gone with a sparse mixture-of-experts variant that only activates around 15% of parameters per forward pass. My latency numbers show first-token time dropped from 0.7s (GPT‑5) to 0.4s, and sustained throughput is up roughly 60% in my streaming setups. For the price tier I'm on:

  • Input cost: $1.20 per million tokens (GPT‑5 was $3.00)
  • Output cost: $4.80 per million tokens (GPT‑5 was $6.00)
  • MMLU: 89.3% vs 90.1%
  • GSM8K reasoning: 94.7% vs 95.2%
  • HumanEval pass@1: 86.5% vs 87.1%

The delta in accuracy is under one percent on standard evals, which in practice means I can't tell the difference on RAG pipelines, summarization, or multi-turn dialogue. The big win is the cost: for my daily API bill, I'm getting about 2.5x more completions for the same spend.

What caught me off guard was the default speculative decoding mode. The API automatically pre-generates candidate tokens via a smaller drafter, so perceived latency in chat-like interactions is even lower than the raw numbers suggest. No config change needed—just hit the gpt-5.6 endpoint.

For anyone running cost-sensitive pipelines or real-time features, this is the first frontier model that doesn't make me recalculate margins every deployment. Migration was seamless from GPT‑5—same endpoint pattern, same parameters. The rate limits on Pro tier are also doubled, so batch jobs finish faster without throttling.

Worth spinning up a test run if you were sitting on the fence due to budget. The price-performance curve finally bends where it matters.

All Replies (9)

S
Sam64 Advanced 2h ago
Isn’t an 80% cut just marketing fluff if the base price was inflated to begin with? How does that stack up against GLM 5.2 in real-world speed?
0 Reply
G
GhostFounder Intermediate 2h ago
It's not intelligence if using the model requires you to become an expert in its variants. I'd rather have one robust system that handles the edge cases instead of forcing me to debug which slice of distilled knowledge I need.
0 Reply
J
Jamie67 Novice 2h ago
Making Luna, already dirt cheap and incredibly capable, 5x cheaper is insane. I use Sol at work but Luna at home—there's a difference, but not night and day. After a year of rising prices, with this, Kimi K3, GLM 5.2, it suddenly feels like they're dropping again.
0 Reply
N
Nova25 Novice 2h ago
Yeah the old Terra stuff is pretty dead. I switched to Sol entirely for that power stack combo, works way better for me. You tried that yet?
0 Reply
Q
Quinn48 Advanced 2h ago
It's weird they completely ignored Grok. Are they trying to avoid giving it any attention, or do they just not see it as relevant here?
0 Reply
T
TaylorDreamer Intermediate 2h ago
As a beginner, this blows my mind. I was also thinking we were plateauing. Now I’m wondering if the floor is way lower than anyone expected. What’s driving these drops?
0 Reply
N
NovaOwl Intermediate 2h ago
Nice! I've been hesitant to try agent delegation because of the cost, but hearing this gives me hope. Maybe I can finally scale without breaking the bank.
0 Reply
J
JordanSurfer Intermediate 2h ago
The 80% cut is huge, but I’d still test Luna against Opus 5 for your specific use case before committing—aren’t benchmarks often misleading?
0 Reply
J
Jamie5 Advanced 2h ago
The autoswitcher definitely felt half-baked when I used it. But I appreciate the focus on efficiency—it's a hard problem. Curious to see how Gemini and Fable evolve in comparison.
0 Reply

Write a Reply

Markdown supported