Today, we are releasing a significant update to our Cache Hit Rate (CHR ) calculation. This revised formula will take into account all cacheable traffic, including HITs, MISSes, and now PASSes that could potentially be cached.

What does this mean for your Stellate services

You might notice a noticeable decrease in the CHR value for your service. However, it's essential to understand that this doesn't imply a sudden decrease in your cache performance. Instead, it results from the new, more comprehensive calculation formula.

Why did we made this change

This decision has been driven by deep thought and consideration, in alignment with our mission to provide the most relevant and meaningful data for your caching needs. We aim to make the CHR metric more accurately represent the cacheable traffic, allowing for deeper insights, such as revealing the Max CHR for specific operations

We hope this provides transparency into the change, you learn more about caching in our docs. If you have any questions or concerns, please reach out to our support team at support@stellate.co.