Claude Prompt Cache Diagnostics: Stats Thread Reveals 98.9% Cache Read Ratio
Two days ago, Anthropic released the prompt cache diagnostics feature in Claude Console. It's a tool for developers to understand why a request misses the cache and to reduce costs. One developer (u/samuelroy_) shared their stats in a community thread, aiming to find patterns and improve cache performance across the board.
Key Stats from the Source
- Overall cache read ratio: 98.9%
- 80% of cache misses are due to
messages changed. - Write amortization for Sonnet: 3.69x
The developer noted that their project harness is designed to only append messages in history, making the high miss rate from messages changed surprising. The likely explanation is users forking conversations, which changes the message chain.
What This Means
Prompt caching reduces cost and latency. With a 98.9% read ratio, the developer is already efficient, but the diagnostic data reveals a clear area for improvement: reducing unnecessary message changes. If you see similar patterns, auditing how conversations are forked or edited could boost cache hit rates.
For reference, write amortization (3.69x for Sonnet) indicates how many times a cache entry is written relative to reads. A lower value is better.
First-party analytics like this are a step forward for AI API cost optimization. Other providers are expected to follow.
📖 Read the full source: r/ClaudeAI
👀 See Also
The double standard in AI-assisted creation: coding vs. writing
A Reddit discussion highlights the contrasting reception between AI-assisted coding (vibe coding) and AI-assisted writing, noting identical workflows but different cultural perceptions.
DeepSeek-V4 Pro and Flash: 1.6T Parameters, 1M Token Context, Hybrid Attention
DeepSeek-V4-Pro (1.6T params, 49B active) and V4-Flash (284B params, 13B active) support 1M token context. New hybrid attention (CSA + HCA) reduces single-token inference FLOPs to 27% and KV cache to 10% of DeepSeek-V3.2.
Agent Memory Is Not a Storage Problem: It's an Authority Problem
A developer argues that agent memory fails not because retrieval misses, but because all notes return with equal authority. The fix: a graph with roles, expiration, and activation fields.
Dangerously Skip Reading Code: When LLMs Write Code Faster Than You Can Read It
What if we stop reviewing LLM-generated code and instead treat it like machine code? Move rigor to specifications and tests.