---
title: "Comment by Julian Neagu on \"Semantic Caching for LLM Calls in ASP.NET Core: When to Use It and How\" | Hashnode"
description: "The cost point hits home. I’ve seen repeated prompts quietly eat through API budgets. Semantic caching helps, but only if you measure the hit rate first."
url: "https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399/comment/6a8453f44e257806c949dd4f"
---

[Discussion](https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399)

Comment [Semantic Caching for LLM Calls in ASP.NET Core: When to Use It and How](https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399)

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Aug 18](https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399/comment/6a8453f44e257806c949dd4f)

The cost point hits home. I’ve seen repeated prompts quietly eat through API budgets. Semantic caching helps, but only if you measure the hit rate first.

[Coding Droplets](https://hashnode.com/@codingdroplets)

[Aug 18](https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399/comment/6a8453f44e257806c949dd4f#reply-6a845dda69281e8b90ec4bc4)

Hi Julian, Thanks! Agreed. Measuring comes first.

One thing I'd add. Hit rate on its own can flatter you. A loose threshold looks like a great result until you check false hits next to it. I measure duplicate rate in shadow mode before building anything, then track both numbers together.
