Table of Contents

Introduction
Role of Cache Variation in Magento
Where Cookies Come Into Play
Understanding Difference Through Code
Why This Matters for Cache Hit Ratio
Core Principle: Be Intentional
Avoiding Cache Fragmentation
Performance Checks to Consider
Final Thaughts

Varnish, Cache Hit Ratio, and Cookie Context for X-Vary in Magento

How a Small Cookie Can Cost You 20% Cache Hit Ratio

In Magento, Varnish is one of the most powerful tools for improving frontend performance. When configured and used correctly, it can significantly reduce page load times and server load by serving cached content instead of repeatedly generating pages. However, this efficiency depends heavily on how well cache variation is controlled.

A frequently overlooked cause of poor Varnish cache performance in Magento is excessive variation in the X-Magento-Vary header triggered by cookies. When non-essential cookies influence the vary string, it leads to cache fragmentation, reducing cache efficiency and hit ratio in a measurable way.

The Role of Cache Variation in Magento

Magento does not serve the same cached content blindly to all users. Instead, it intelligently varies cache based on specific conditions using HTTP context. This ensures that users see the correct version of a page depending on factors like login status, store view, or other contextual data.
This variation is managed through the X-Magento-Vary header. Every value added to the HTTP context contributes to this header, which in turn becomes part of the cache key used by Varnish.

In simple terms:

Each unique combination of context values creates a separate cache entry.
The more variations you introduce, the more fragmented your cache becomes.
Fragmentation leads to lower cache reuse and reduced performance benefits.

Where Cookies Come Into Play

Cookies are often used in Magento projects to store small pieces of user-specific data. This could be anything from preferences to tracking values or temporary session-related flags.
On their own, cookies do not necessarily impact caching. The problem begins when these cookie values are tied to the HTTP context and, by extension, the X-Magento-Vary header.
When a cookie value is added to HTTP context:

Every unique cookie value becomes part of the cache key.
Varnish treats each variation as a completely separate page.
Cache entries multiply rapidly.

This is where performance degradation starts to show.

Understanding the Difference Through Code

Let’s look at two implementation patterns to understand how small changes can have a big impact.

Example 1: Cookie Without Impact on X-Magento-Vary

$cookieMetadata = $cookieMetadataFactory->createPublicCookieMetadata()
->setDuration(3600)
->setPath('/')
->setHttpOnly(false);

$cookieManager->setPublicCookie(
'my_cookie',
'some_value',
$cookieMetadata
);

// No httpContext usage

In this example:

A cookie is created and set.
The value is stored on the client side.
However, it is not added to HTTP context.

Result:

The cookie does not influence cache variation.
Varnish continues to serve the same cached page across users.
Cache hit ratio remains stable.

Example 2: Cookie That Impacts X-Magento-Vary

$cookieMetadata = $cookieMetadataFactory->createPublicCookieMetadata()
->setDuration(3600)
->setPath('/')
->setHttpOnly(false);

$value = 'some_value';

$cookieManager->setPublicCookie(
'my_cookie',
$value,
$cookieMetadata
);

$httpContext->setValue(
'my_cookie',
$value,
true
);

In this version:

The same cookie is created.
But now, its value is explicitly added to HTTP context.

Result:

The cookie becomes part of the X-Magento-Vary header.
Each unique value generates a new cache variation.
Cache entries increase significantly.

Why This Matters for Cache Hit Ratio

The difference between the two examples may look minimal, but the impact is not.
When a cookie is added to HTTP context:

Even a small set of values can multiply cache entries.
If the value changes frequently, the number of variations grows rapidly.
Varnish struggles to reuse cached pages effectively.

This directly affects cache hit ratio:

Lower hit ratio means more requests reach the application.
Increased backend processing leads to slower response times.
Server load increases unnecessarily.

In real-world scenarios, this kind of implementation can easily reduce cache efficiency by 10–15%, and in some cases even more.

The Core Principle: Be Intentional

The key takeaway is not that cookies are problematic, but that their usage must be intentional.
Not every cookie should be part of HTTP context.
Before adding any value to X-Magento-Vary, ask:

Does this value actually change the rendered HTML?
Will two users with different values see different content?
Is this variation essential for correctness?

If the answer is no, then the value does not belong in HTTP context.
In fact, most cookies used in typical implementations do not influence the final HTML output and therefore should remain outside the cache variation mechanism.

Avoiding Cache Fragmentation

Cache fragmentation occurs when too many variations are created for what is essentially the same page. This reduces the likelihood of cache reuse and undermines the purpose of using Varnish.
Common causes include:

Adding non-essential cookie values to HTTP context
Using dynamic or frequently changing values in cache keys
Over-engineering personalization at the cache level

By limiting variation only to necessary factors, you can:

Improve cache reuse
Increase hit ratio
Deliver faster responses to users

Performance Checks to Consider

To understand whether this issue is affecting your store, it’s important to evaluate your current setup.
Start by asking:

What cache hit ratio are you currently seeing on Varnish?
Have you reviewed your X-Magento-Vary header values?
How many variations are being generated for key pages?

Additionally:

Check Varnish logs to inspect X-Magento-Vary values
Identify whether unnecessary context values are being added
Look for patterns where cookie-driven variations are excessive

These checks can quickly reveal whether cache fragmentation is impacting performance.

Final Thoughts

Varnish can deliver excellent performance improvements in Magento, but only when cache variation is carefully managed. The interaction between cookies and the X-Magento-Vary header is a subtle but critical part of this process.
A small implementation decision like adding a cookie value to HTTP context can lead to a significant drop in cache efficiency. Over time, these decisions accumulate, resulting in lower cache hit ratios and slower site performance.
The solution is straightforward: