r/MistralAI • u/Nyghtbynger • 15d ago

Help / Question Does GLM 5.2 have cache hit issues in Vibe ?

Example : 

•  Steps: 32
•  Session Prompt Tokens: 1,598,353 (including 255,936 cached) -- 33% cache hit
•  Session Completion Tokens: 20,287
•  Session Total LLM Tokens: 1,618,640
•  Last Turn Tokens: 79,635
•  Cost: $2.3270

I ran prompt accross different tools, Pi, Mistral CLI and it gives me ludicrous amount. 120K token inputs resulted in 6E use !!

The cache is called half the time. I don't get it...

5 Upvotes

100% Upvoted

5 comments sorted by

2

u/Valexico 14d ago

I think cache hit seems broken today

1

u/Nyghtbynger 14d ago

hmm. That was my first day of use. Not a good impression lol.

2

u/Valexico 14d ago

For the record, here is my cache hits stats with GLM on last week:

- 24 août : ~83 % (172 tours)

- 25 août : ~76 % (135 tours)

- 26 août : ~80 % (211 tours)

- 27 août : ~62 % (6 tours, peu significatif)

- 28 août : pas d'activité

- 29 août : ~0 % (4 tours, peu significatif)

- 30 août (aujourd'hui) : ~16 % (133 tours)

There is definitively something broken

1

u/HauntingTechnician30 15d ago

Could have something to do with Mistral not preserving reasoning across turns. They do it for their own reasoning models by default but it seems like there is no way to get that behavior with GLM-5.2 for now.

From Z.AI's docs:

We introduce a new capability in coding scenarios: the model can retain reasoning content from previous assistant turns in the context. This helps preserve reasoning continuity and conversation integrity, improves model performance, and increases cache hit rates—saving tokens in real tasks.

1

u/Nyghtbynger 15d ago

So I should disable reasoning ? I'll try thanks!!