Earlier quoted context omitted.
They’re nondeterministic at a fine level, but can be “deterministic” at a more general level: e.g. you might know that one model will always return properly formatted json when asked. That might not be true of the replacement, even if it is in general “better” and cheaper. Just the risk of such a thing means regression testing every time you update the model, and you want to be able to run that testing on your schedu…
> They’re nondeterministic at a fine level, but can be “deterministic” at a more general level: e.g. you might know that one model will always return properly formatted json when asked. That might not be true of the replacement, even if it is in general “better” and cheaper. This isn't true. Even Sol messes up JSON formatting for me on occasion. Do not delude yourself into thinking these things are reliable. They are…
DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
141–150 of 221 posts
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#142>In keeping with our commitment to user responsibility, following the official launch of V4.1 Flash and prior to the release of V4.1 Pro, all requests to the Pro model will be routed to V4.1 Flash and billed at Flash's price Please don't do this kind of thing. If a user has validated a workflow on V4 Pro, they might not want to suddenly start testing it in production on V4.1 Flash. Instead, keep V4 Pro around but dep…
LLMs add enough nondeterminism to a workflow. Swapping them without the user knowing adds substantially more.
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#143Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#144I was getting something like 300-400 tok/s which was just insanity. It was running so much faster than the toolcalls themselves. Honestly, even if it's not quite as strong in reasoning, it just throws so much so fast that it can do a lot more than you might expect.
I'd say it was comparable with GLM5.3 Flash.
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#145If they can keep up this cadence of Flash leap-frogging the previous Pro, we're in for a good time
Anthropic/OpenAI might step up their anti-distillation defences though.
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#146Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#147>In keeping with our commitment to user responsibility, following the official launch of V4.1 Flash and prior to the release of V4.1 Pro, all requests to the Pro model will be routed to V4.1 Flash and billed at Flash's price Please don't do this kind of thing. If a user has validated a workflow on V4 Pro, they might not want to suddenly start testing it in production on V4.1 Flash. Instead, keep V4 Pro around but dep…
if you want deterministic returns, you should set the temperature to 0 to get the best possibility of deterministic.
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#148>In keeping with our commitment to user responsibility, following the official launch of V4.1 Flash and prior to the release of V4.1 Pro, all requests to the Pro model will be routed to V4.1 Flash and billed at Flash's price Please don't do this kind of thing. If a user has validated a workflow on V4 Pro, they might not want to suddenly start testing it in production on V4.1 Flash. Instead, keep V4 Pro around but dep…
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#149>In keeping with our commitment to user responsibility, following the official launch of V4.1 Flash and prior to the release of V4.1 Pro, all requests to the Pro model will be routed to V4.1 Flash and billed at Flash's price Please don't do this kind of thing. If a user has validated a workflow on V4 Pro, they might not want to suddenly start testing it in production on V4.1 Flash. Instead, keep V4 Pro around but dep…
Re: DeepSeek launching v4.1 flash cheaper and more capable than v4 pro
#150Earlier quoted context omitted.
Usually I would very much agree with you, but those things are not deterministic so if that's an issue for you you're probably not making the right choices.
Nope, strong disagree. The model is one small part of the process harness; behaviors are usually routable with expected propensities. Unexpected model changes avoiding change management messes with monitoring and observability thresholds. Stochastic controls are a real thing when you have your distributions defined; your workflows on a new model will throw that expected prior out the window.
Also in principle it's similar to Anthropic downgrading.
Personally I use the basis that if I don't self host (I include remote host, but that I pay per hosting nor per model or api), it can change behavior without me asking. But they shouldn't, but it doesn't matter that's what they do.