---
title: "Comment by Kartik N V J K on \"Semantic Caching for LLM Calls in ASP.NET Core: When to Use It and How\" | Hashnode"
description: "The threshold tuning is where semantic caching quietly gets dangerous, since a threshold loose enough to catch paraphrases will eventually serve a cached answer"
url: "https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399/comment/6a831f70e4f4eb6bf6f61ed3"
---

[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)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

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

The threshold tuning is where semantic caching quietly gets dangerous, since a threshold loose enough to catch paraphrases will eventually serve a cached answer to a question that only looks similar but needs a different reply. I keep a small labeled set of near-miss pairs and measure false-hit rate whenever I move the threshold, so a cost win does not turn into a wrong-answer regression. How are you deciding your similarity cutoff, and do you track how often a hit returns a semantically-off answer?

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

[Aug 17](https://hashnode.com/posts/semantic-caching-llm-aspnet-core/6a81a679863aa920fefe8399/comment/6a831f70e4f4eb6bf6f61ed3#reply-6a832d37e4c3be87f2869cde)

Hi Kartik, Thanks! Threshold tuning is the part most people skip.

No fixed number. The distribution shifts with the embedding model, so I shadow-run the cache for a week, log top scores without serving anything, then label a few hundred real pairs and find where false hits fall off.

On tracking, rephrase rate is the giveaway. If people re-ask more after a hit than a miss, the threshold's too loose.

Thanks again for sharing yours.
