Hacker News new | ask | show | jobs
by baalimago 1 day ago
We swapped an internal system from gpt-5-mini to gpt-5.6-luna and saw no benefit but 4x cost. Sufficed to say: we swapped back to gpt-5-mini.
3 comments

Experienced similar between 5.4-mini vs 5.6-luna in our own pipelines but after spending some time on prompt optimization and testing out various reasoning effort levels 5.6-luna was well worth it. Did you just replace model selection while keeping everything else in place or spend some time on evaling with newer prompts etc?
No we kept prompts as is, just swapped model. The prompt is already quite optimized for the task. How would updating it possibly make a more intelligent model spend less tokens than a less intelligent model? Care to elaborate?
Most of the time when upgrading models we have needed to change prompts to get the same performance (let alone better performance). Usually, your prompt is overfit to the specific model doing the specific task. For example often your previous prompt is overspecifying and creating contradictions that a dumber model would just gloss over whereas a smarter model will try even harder to follow.
I think the fundamental difference between our assumptions is you believe prompts to be optimized for tasks rather than model-task pairs. The only elaboration I can give you is empirical observations and model providers own guidance (as someone has already linked here). I'm pretty sure you probably have specific parts of your prompts that came about due to specific failure modes observed in your evals of running the task against first model. These vary across models in my experience, and it's always worth redoing this calibration process.
Yikes, you can't really expect prompts to just be model agnostic
Here is an example of a guide from OpenAI on how you should prompt 5.6 differently than their previous models.

https://developers.openai.com/api/docs/guides/latest-model#p...

5.6 class models have a brand new caching architecture. Make sure you were using the prompt cache breakpoints and cache keys correctly - it's much different than < 5.5 and makes a huge difference for many production workloads.
So now presumably it'd at least be roughly equal cost, or maybe a little less?