I've directly inspected calls for pro/Max plans and as of today they have 1hr cache expiries. This has definitely degraded to 5 min in the past but that's the behavior today.<p>If you're paying API rates, you can choose 5m or 1hr yourself (and pay different rates).<p>Keeping a 1hr cache warm could still be useful, sure, but outside that, I don't see much use of this today.
Is the 5-minute expiration correct? I thought it was more like ~1 hour.
Feels like will be shut down real quick
Yes, this wastes cycle. They dump your cache and deallocate the VMs so that others can use it. This will result in tokens wasted and downtime for others.
Why? Seems fine if people want to burn more cache reads.
Glad this exists. It will force anthropic to fix their flawed cache mechanism.
Don't we pay for cache input though?
You can send and receive 1 byte and refresh the cache. Keeping the cache alive isn't free, but it's close.
The idea is this keeps it in cache so you don’t have to pay to re-input.
This is a good idea if it could manage it in an acceptable way.<p>For example, there might be something I intended to complete in one sitting, but took two sittings in the same day unexpectedly. Maybe it could just be a few cache delays per day or something, tagged in advance somehow.
[dead]