I think you're arguing the same general point that the person you're responding to is. But you're saying he's not understanding - he understands that they report a cache hit % but you can't look at that public metric with any level of accuracy _because_ most people aren't pinning their providers and they _are_ getting juggled around which is bringing that metric down. That's not to say that specific providers might have issues or worse cache implementations - but it stands that if openrouter is juggling the requests back and forth by default then _that alone_ is breaking caches on those requests in huge numbers.

▲

dakolli a day ago | parent [-]

I know what they're saying. Why would openrouter calculate it thay way lol. They obviously dont. Think for a sec, they arent idiots.

▲

irthomasthomas 20 hours ago | parent | next [-]

Something is up. Deepseek cache hit rate on zenmux is 98%, but only 85% via openrouter.

▲

RussianCow a day ago | parent | prev [-]

How else would you expect them to calculate it?

▲

dakolli 17 hours ago | parent [-]

Do you really think they're docking points because cache invalidation due to provider switching? Seriously llms are frying ya'lls brain.

	▲	RussianCow 13 hours ago \| parent [-]
		They're not "docking points", they're calculating it in the most straightforward way. If I start a session and the majority of requests are sent to Provider A, and my last request gets routed to Provider B, I have a 0% cache hit rate with Provider B. I'm very curious how else you expect this to be calculated? Do you think they're completely omitting requests that switch providers mid-session? FWIW, I get significantly higher than listed cache hit rates when I pin my session to a specific provider, which is further evidence of the above.