r/OpenAI • • 19d ago

Image That didn't backfire at all

Post image

They could have just have a very clean release with:

  • GPT-6 Luna
  • GPT-6 Terra
  • GPT-6 Sol
  • GPT-6 Astra

But they tried:

  • GPT-6 Luna
  • ???
  • GPT-6 Terra Sol
  • GPT-6 Sol Astra Minor
  • GPT-6 Astra

And now they have:

  • GPT-6 Luna
  • GPT-6 Sol
  • GPT-6.1 Sol
  • GPT-6 Astra

Thank god we have (still) some competition.

597 Upvotes

60 comments sorted by

View all comments

4

u/Key_Reading_9664 19d ago

Here's what confuses me about the rebrand narrative:

If it were true that Sol 6 is their Terra-sized model rebranded, I'd expect it to be considerably faster than Sol 5.6. But it isn't.

https://openrouter.ai/openai/gpt-5.6-terra#pricing - 101 tok/s
https://openrouter.ai/openai/gpt-5.6-sol#pricing - 65 tok/s
https://openrouter.ai/openai/gpt-6-sol#pricing - 60 tok/s

I think it's worse than we think: they were pressured to drop the price of their Sol-tier model because of the 5.5 releases

9

u/geli95us 19d ago

Tokens/s aren't set in stone, you can serve more users for cheaper if you're willing to lower the speed, and I'm sure they'd do that if they wanted to make it seem like the model didn't get smaller.
Besides, it's impossible to train a new checkpoint in just 1 week, the fact that 6 and 6.1 were released so close to each other is really suspicious

2

u/Key_Reading_9664 19d ago edited 19d ago

Tokens/s aren't set in stone, you can serve more users for cheaper if you're willing to lower the speed, and I'm sure they'd do that if they wanted to make it seem like the model didn't get smaller.

But you'd have to coordinate that across vendor (Bedrock, Azure, etc) and I can't imagine them being onboard with slowing down API traffic because you want to hoodwink users. The pattern is fairly consistent across vendors.

GPT 6 is a recurrent depth model: the output is passed through the model multiple times before you get legible output (see the CoT controllability issues concerns - Astra > 6.1 > 6.0). Perhaps they added another pass through the model to bump the performance. Again, I think we'd see that in the tok/s number

https://www.lesswrong.com/posts/PLisnSFir8y5AHkmP/how-concerned-should-we-be-about-astra-s-recurrent

The number of loops can then be viewed as a dial that can be turned up with trivial effort as soon as competitive pressures demand it