📊 State of Magento 2025

The Home for Magento 2 Excellence

Quality-tested Magento 2 modules. Explore. Evaluate. Elevate. #magento2

613 Modules
401 Ready
211 Need Help
🏆 Leaderboard
Actively Maintained v2.0.1

Module Optimize Cache Size

vendic/module-optimize-cache-size

Reduces cache keys by removing product/category specific layout handles. Improves performance by decreasing cache size and average Redis TTL.

45,225
Downloads
Below average
34
GitHub Stars
Below average
12d ago
Last Release
4
Open Issues
Build Passing
Ready to install

Build Tests

Composer Install
DI Compile
Templates

Code Quality

CS Coding Standard
15 warnings
L5 PHPStan

Tested on Magento 2.4.8-p3

Recent Test History

Each release is tested against the latest Magento version at that time.

v2.0.1 on Magento 2.4.8-p3
Jan 30, 2026
v2.0.0 on Magento 2.4.8-p3
Dec 26, 2025

Share This Module's Status

Module Optimize Cache Size Magento compatibility status badge

README

Loaded from GitHub

Vendic_OptimizeCacheSize

Magento 2 extension that reduces the number of cache keys by removing catalog_product_view_id_, catalog_product_view_sku_, catalog_product_view_attribute_set_, catalog_category_view_id_ layout handles by default,

This means that you lose the option to have product/category specific layout handles (both through the use of XML files in your installation and through the use of Design > Layout and Design > Custom Layout Update on the category and product edit pages in the admin), unless you re-enable them via the configuration.

Configuration: Stores -> Configuration -> Vendic -> Optimize Cache Size

Installation

composer require vendic/module-optimize-cache-size

Related discussions

Results

Here's a some real life results from a Magento 2.4 instance with 7k products and 1.5k categories:

number cache keys

cache ttl

The arrow marks the release of this extension. You can clearly see the results. Cache keys were reduced 50% (or more). Average Redis TTL also dropped significantly.

This content is fetched directly from the module's GitHub repository. We are not the authors of this content and take no responsibility for its accuracy, completeness, or any consequences arising from its use.