Virtually every task I give to either is better served by going up a tier and down a reasoning level, or down a tier and up a reasoning level. I simply don't understand their use case. No testing I've done has shown them to have a niche where there isn't a cheaper-with-equal-results or more-performant-at-same-cost option.
[–] h14h 3 days ago
[–] daynthelife 3 days ago
Spinning up a fresh session would be a reasonable choice in the above case, but sometimes you still need the retained context.
[–] fy20 3 days ago
[–] h14h 2 days ago
Terra 6.1 on low reasoning outperforms Luna 6 on max reasoning, while costing half as much per task and completing each task over 10x faster (per AA v5).
Luna 6.1 will likely close the intelligence & cost gaps, but that speed advantage will remain.
[–] dannyw 3 days ago
Benchmarks don’t really tell you much. For API best will always be a model+effort sweep on your internal evals (and if you don’t have internal evals, do that first).
For individual coding harnesses, honestly I just go with vibes. The best workflow is the one that works for you.
[–] foretop_yardarm 3 days ago
[–] selcuka 3 days ago
[–] eknkc 3 days ago
On subscription for coding and stuff I am basically on Astra Ultra all day long.
[–] legulere 3 days ago
https://docs.github.com/en/copilot/reference/ai-models/suppo...
[–] onlyj 3 days ago
[–] nfw2 3 days ago
[–] datadrivenangel 3 days ago
[–] nfw2 3 days ago
2. There are rote or simple tasks where higher reasoning isn't needed and one model vs the other wouldn't even be distinguishable.
3. How many tokens are used during reasoning depends as much on the task as the reasoning level.
4. Sonnet is faster and half the price per token, so Opus will only be cheaper if it can spend fewer tokens. This won't be the case for all tasks. Opus and Sonnet will also consume the same number of tokens to load context, so the relative price comparison depends a lot on where the task is context-heavy or reasoning-heavy.
[–] datadrivenangel 3 days ago
What are you smoking and can I have some?
[–] nfw2 2 days ago
[–] moecables 3 days ago
[–] hobofan 3 days ago
I have some business automation process for some customers that I maintain, where Terra with low reasoning ended up with the best price/performance & latency. With an equivalent Luna with high reasoning, price was usually better, but quality had a higher variance (very much depends on where the thinking takes the model) and latency for high reasoning was worse.
[–] rfgplk 3 days ago
[–] Silagi 3 days ago
[–] rfgplk 3 days ago
[–] InsideOutSanta 3 days ago
[–] qert12 3 days ago
To justify the pricing of Sol and Astra. Old business trick.
[–] jhatemyjob 3 days ago
[–] handzhiev 3 days ago
[–] notatoad 3 days ago
if you're just talking about use in codex or claude code, then sure, leave it on opus all the time. but for running routine api requests, sonnet is great.
[–] datadrivenangel 3 days ago
I think it's also a fake lever to give to finops / it teams to try and keep costs down.
[–] Sha1rholder 3 days ago
Take a look at this reply.
If you pay API prices for inference in your product stack & have specific use-cases w/ custom evals, these smaller models provide an additional cost/speed lever to adjust. Ultimately, I think the point is to compete on cost for use-cases where Sol on the lowest reasoning is overkill.
If you have a fairly straightforward usecase where Terra performs just as well as Sol, but is faster and cheaper, why not use it?