111–120 of 221 posts
DeepSeek v4 Flash with high is already a really great work horse. Reliable. But this time, not only that it is better but they are reducing the price by 50% so that's great. I also find the DeepSeek models to be more precise than Claude models (last I used 4.7) in that I yet had not the occasion where model did something unintentional that I did not direct it to. EDIT: Updated percentage reduction.
Earlier 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.
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…
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 not.
>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…
You absolutely cannot consider an LLM production build number something to be pinned against as a static dependency in a product chain, so it's a non-issue.
Sounds nice! But, the web ui chat version of flash has very poor language following abilities in my experience: You may ask it something in English, and get a thinking chain in Chinese with an answer in Chinese, or an English thinking chain and an English answer. Using the retry button on the same question has a 50/50 chance of any of those results. Sometimes, asking something in English, but where information are mo…
I take the free chat gpt one writ with it in polish suddenly english.
Sounds nice! But, the web ui chat version of flash has very poor language following abilities in my experience: You may ask it something in English, and get a thinking chain in Chinese with an answer in Chinese, or an English thinking chain and an English answer. Using the retry button on the same question has a 50/50 chance of any of those results. Sometimes, asking something in English, but where information are mo…
It's not just web chat, V4 Flash 7/31 suffers from a lot of pathological behavior in coding harnesses as well, e.g. infinite loops, hallucinations, premature termination, and invalid tool calls.
Earlier quoted context omitted.
Reducing the price by 100% means it’s free. I think you mean reducing the price by 50%
What I mean is that price has been effectively halved. During off-peak hours, the unit price is reduced from $0.007 for input cache hits to $0.003, $0.22 for input cache misses to $0.15, and $0.12 for output to $0.6
0.15/0.22 ≈ 0.68, meaning a roughly 32% reduction on inputs. The 50% reduction is only outputs and cached inputs.
Earlier quoted context omitted.
I finally uninstalled the app yesterday after giving it plenty of chances over several months. Yesterday, I asked it whether «DeepSeek has fixed the issue where it erroneously answers in Chinese?» and it answered in Chinese.
So you did not do what the post you replied to suggested?
Earlier quoted context omitted.
Reducing the price by 100% means it’s free. I think you mean reducing the price by 50%
What I mean is that price has been effectively halved. During off-peak hours, the unit price is reduced from $0.007 for input cache hits to $0.003, $0.22 for input cache misses to $0.15, and $0.12 for output to $0.6
Earlier 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.
Models are not deterministic, but they do have a flavor . When that flavor changes it can change the nature of output in a way that is undesirable. Sort of like shooting a rifle - where the bullets hit is (to some order of magnitude, no philosophizing please) non-deterministic, but different very similar rifles will group differently and need to be appropriately adjusted to hit anything.
That flavor profile is known -- it's typical behavioral distribution is somewhat understood (and, often, common failure modes addressed). If JSON breaks about 20% of the time, and that drops for 2% or blows up to 90%, it can drive all sorts of issues (not the least, costs for retries).