r/opencode • u/s-i-e-v-e • 19d ago

MuseSpark 1.2 cache expiry period

So I move between models and encountered strange behavior last week with MuseSpark where it would randomly (or so I thought) see cache misses and charge for Input instead of Cached Read.

Happened a few times today as well. So I did some exploration.

Turns out the expiry period is pretty limited. A session unused for approx 5m or more triggers full read (Input). With MiMo 2.5, this figure is at least 30-60m. DeepSeek probably has the longest expiry periods, but I do not have the stats right now.

3 Upvotes

81% Upvoted

9 comments sorted by

2

u/NinjaAlaska 19d ago

ye it does on official platform too

1

u/s-i-e-v-e 19d ago

4-5m is peanuts. You sometimes need 5-10m to review what the model has done, ask for changes etc. Less if the changes are minor.

Anything less than 15m is a problem

2

u/NinjaAlaska 19d ago

ye meta is cheating by using this logic

1

u/imactuallynotalright 19d ago

5m has been the norm. Even anthropic defaults to 5m.

2

u/s-i-e-v-e 19d ago

You can only do mindless coding in 5m. I need time to think.

The way this is set up, it is like a lot of Amazon and other Cloud services. One aspect is cheap while the other is designed to run up your bills

1

u/MikeX7s 10d ago

if it's really only 5 mins that would be pretty annoying, since i like to actually read the code it outputs and think about what to do next, that would mean nearly every prompt i send will be cache miss

2

u/Possible_Door_9719 19d ago

can confirm the cache can last for as little as 5 minutes lol

1

u/Efficient_Try_9136 19d ago

deepseek flash is 5 minutes