WooCommerce support?

[MrGKanev]

Hi,

As far as I can see, nothing stops MilliCache from working on WooCommerce stores, but has anyone tested it on larger installs?

In my case, I don’t currently have enough time to test it on bigger stores (around 10k products), so I was wondering if anyone here has already tried it and could share their experience. Any issues or things to watch out for? How much memory/space you needed in Redis for such a store?

Hi @MrGKanev, great question!

MilliCache respects the DONOTCACHEPAGE constant, which WooCommerce sets on pages like cart, checkout, and my-account. So those pages are automatically excluded from caching — no configuration needed.

You should add the Sourcebuster tracking cookies (sbjs_*, used by WooCommerce's Order Attribution feature since 8.5+) to the Ignored Cookies list. So that they do not generate cache variants. In wp-config.php:

define( 'MC_CACHE_IGNORE_COOKIES', [
    ...
    'sbjs_*',
] );

Or configure it in Settings → MilliCache → Ignored Cookies in the admin UI.

Redis memory for ~10k products

Memory depends on the number of unique cacheable URLs, not product count. A 10k-product store with category archives, pagination, and filters might generate 15–20k cached pages. With gzip enabled (default), each page is typically 10–30 KB:
15k pages × ~20 KB ≈ 300 MB

Well within what a modest Redis instance handles. Monitor with wp millicache stats or redis-cli INFO memory.

Things to watch out for:

• Cart fragments: WooCommerce loads these via AJAX (?wc-ajax=get_refreshed_fragments) — MilliCache doesn't cache AJAX/POST requests, so this works automatically.
• Personalized content (e.g., "Recently Viewed"): Typically JS-driven and works fine with full-page caching.

If you get a chance to test on a larger install, would love to hear how it goes!