25% more usage sounds about right given the other token costs are down about 20%? I don't think cache read is a big portion of the overall cost.
> I don't think cache read is a big portion of the overall cost.
For long running tasks it is. That's what made Deepseek so cheap.
Anything with long context quickly gets dominated by cache reads. Especially for interactive sessions I’ve got cache read % between 95% and 98%.