Magento 2 Hosting Optimization: Redis, Elasticsearch and Varnish Settings

Magento 2 is one of the most powerful enterprise-level e-commerce platforms, but that power translates to sluggishness on a poorly configured server. Default installations can see page load times of 5-8 seconds. With Redis cache, Elasticsearch, Varnish full-page cache, and PHP-FPM optimization, it's possible to bring this under 1-2 seconds. In this guide, we optimize your Magento 2 hosting infrastructure layer by layer.

Magento 2 Infrastructure Requirements

Magento 2 is a resource-demanding platform. According to Adobe's official system requirements, it requires a minimum of 2 GB RAM, but anything below 4 GB in production causes serious performance issues.

Redis Cache Configuration

Magento 2 uses file-based cache by default. Hundreds of files are read on every page load, creating a disk I/O bottleneck. Switching to Redis reduces cache read times from milliseconds to microseconds. In Magento, Redis serves three purposes: backend cache, full-page cache, and session storage.

// Backend cache - Redis DB 0
'cache' => [
    'frontend' => [
        'default' => [
            'backend' => 'Magento\\Framework\\Cache\\Backend\\Redis',
            'backend_options' => [
                'server' => '127.0.0.1',
                'port' => '6379',
                'database' => '0',
                'compress_data' => '1'
            ]
        ],
        'page_cache' => [
            'backend' => 'Magento\\Framework\\Cache\\Backend\\Redis',
            'backend_options' => [
                'server' => '127.0.0.1',
                'port' => '6379',
                'database' => '1',
                'compress_data' => '1'
            ]
        ]
    ]
],

// Session storage - Redis DB 2
'session' => [
    'save' => 'redis',
    'redis' => [
        'host' => '127.0.0.1',
        'port' => '6379',
        'database' => '2',
        'max_concurrency' => '6',
        'break_after_frontend' => '5',
        'bot_lifetime' => '7200'
    ]
]

Elasticsearch / OpenSearch Configuration

Starting from Magento 2.4+, MySQL-based search has been removed; Elasticsearch or OpenSearch is mandatory. A properly configured search engine delivers millisecond-level search results across thousands of products and provides advanced features like autocomplete, synonyms, and faceted search.

# Elasticsearch configuration
bin/magento config:set catalog/search/engine elasticsearch8
bin/magento config:set catalog/search/elasticsearch8_server_hostname localhost
bin/magento config:set catalog/search/elasticsearch8_server_port 9200
bin/magento config:set catalog/search/elasticsearch8_index_prefix magento2

# Rebuild search index
bin/magento indexer:reindex catalogsearch_fulltext

Varnish Full-Page Cache

Varnish is an HTTP reverse proxy cache. It stores HTML pages generated by Magento in memory and serves repeated requests directly without touching PHP. With Varnish active, page load times can drop from 2-3 seconds to 200-300 milliseconds.

# Configure Magento for Varnish
bin/magento config:set system/full_page_cache/caching_application 2

# Generate Varnish VCL file
bin/magento varnish:vcl:generate --backend-host=127.0.0.1 \
  --backend-port=8080 --output-file=/etc/varnish/default.vcl

# Restart Varnish
systemctl restart varnish

Typical Magento + Varnish architecture:

PHP-FPM Optimization

Magento 2 performs intensive PHP processing on every request. PHP-FPM pool settings directly affect concurrent request capacity. Incorrect configuration either causes requests to queue or the server to run out of memory.

[magento]
user = www-data
group = www-data

pm = dynamic
pm.max_children = 50        ; For 8 GB RAM
pm.start_servers = 10
pm.min_spare_servers = 5
pm.max_spare_servers = 20
pm.max_requests = 500       ; Prevent memory leaks

; PHP settings
php_admin_value[memory_limit] = 756M
php_admin_value[max_execution_time] = 300
php_admin_value[realpath_cache_size] = 10M
php_admin_value[realpath_cache_ttl] = 7200
php_admin_value[opcache.memory_consumption] = 512
php_admin_value[opcache.max_accelerated_files] = 60000

For your Magento 2 e-commerce infrastructure, consider Hosted Cloud cloud servers. With NVMe SSD disks and instant resource scaling, your store stays fast even during peak traffic. For more on e-commerce hosting requirements, check our E-Commerce Hosting guide.

Frequently Asked Questions

Conclusion

Magento 2 hosting optimization consists of four fundamental layers: Redis for backend/session cache, Elasticsearch for fast search, Varnish for full-page cache, and PHP-FPM for concurrent request handling. When you configure these layers correctly, page load times drop below 1-2 seconds and your store remains stable even during peak traffic periods.