{"id":4298,"date":"2026-09-02T08:15:12","date_gmt":"2026-09-02T07:15:12","guid":{"rendered":"https:\/\/voronov.solutions\/?p=4298"},"modified":"2026-09-02T08:15:12","modified_gmt":"2026-09-02T07:15:12","slug":"setting-up-redis-object-cache-for-wordpress-and-woocommerce-advanced-optimization-and-typo-removal","status":"publish","type":"post","link":"https:\/\/v2.voronov.uk\/en\/blog\/nalashtuvannia-redis-object-cache-dlia-wordpress-ta-woocommerce-pokrokova-optymizatsiia-ta-usunennia-typovykh-pomylok\/","title":{"rendered":"Configuring Redis Object Cache for WordPress and WooCommerce: Step-by-Step Optimization and Troubleshooting Common Issues"},"content":{"rendered":"

Redis Object Cache for WordPress and WooCommerce<\/strong> is a server-side caching technique that stores SQL query results, options objects, and transients in RAM. It solves the problem of high latency (TTFB) on dynamic pages where static page caching does not work: in the cart, on the checkout page, and in the user's personal account.<\/p>\n

Why static cache doesn't work in WooCommerce and how Redis helps<\/h2>\n
\"Why<\/figure>\n

For most WordPress information pages, classic HTML caching (e.g. via Nginx FastCGI Cache, LiteSpeed, or NGINX\/WP Rocket plugins) is sufficient. However, for WooCommerce online stores, this approach has significant limitations. According to official WooCommerce recommendations<\/a>, endpoints such as \/cart\/<\/code>, \/checkout\/<\/code> and sessions of authorized buyers are fundamentally not subject to static caching, as they display personalized data.<\/p>\n

When a user adds a product to their cart, each click generates dozens of complex SQL queries to the MySQL database (product metadata, balances, discount rules, sessions). Without object caching, the database becomes a \u00abbottleneck\u00bb, causing server response delays (TTFB > 1\u20132 seconds), which directly worsens behavioral factors. We wrote more about this in the article about, How website loading speed affects SEO and sales<\/a>.<\/p>\n

In accordance with WordPress documentation WP_Object_Cache<\/a>, wordpress object caching is designed to intercept repeated database accesses. Redis stores processed PHP objects directly in RAM, returning them in fractions of a millisecond.<\/p>\n

Interaction architecture: PHP-FPM, Redis and MySQL<\/h2>\n
\"Interaction<\/figure>\n

The query workflow with Redis connected looks like this:<\/p>\n

    \n
  1. User request:<\/strong> The browser accesses a dynamic page (for example, a shopping cart).<\/li>\n
  2. Checking the cache:<\/strong> PHP script via object coupler (object-cache.php<\/code>) checks for the presence of the required objects in Redis.<\/li>\n
  3. Cache Hit:<\/strong> If data is found in RAM, it is immediately returned to PHP. The query to MySQL is not executed.<\/li>\n
  4. Cache Miss:<\/strong> If there is no data, PHP makes a query to MySQL, gets the result, writes it to Redis for future queries, and returns the response to the user.<\/li>\n<\/ol>\n

    Connection Configuration: Unix Domain Sockets vs TCP\/IP<\/h2>\n

    When setting up Redis on the same server as the website (localhost), using a TCP\/IP network socket creates unnecessary overhead at the operating system level. Redis configuration documentation<\/a> recommends using Unix domain sockets for local connections, which significantly reduces the load when configuring redis on the server.<\/p>\n\n\n\n\n\n\n\n
    Parameter<\/th>\nTCP\/IP (127.0.0.1:6379)<\/th>\nUnix Socket (\/var\/run\/redis\/redis-server.sock)<\/th>\n<\/tr>\n<\/thead>\n
    Latency<\/strong><\/td>\nHigher (passing through the network stack)<\/td>\nMinimal (IPC)<\/td>\n<\/tr>\n
    Capacity<\/strong><\/td>\nLimited by TCP stack<\/td>\nHigher by 15\u201330% for local processes<\/td>\n<\/tr>\n
    Security<\/strong><\/td>\nRequires firewall\/bind configuration<\/td>\nProtected by file system permissions<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    1. Settings in redis.conf<\/h3>\n
    unixsocket \/var\/run\/redis\/redis-server.sock unixsocketperm 770 # Disable TCP if Redis is running purely locally port 0<\/code><\/pre>\n
    Make sure the user www-data<\/code> (or PHP-FPM user) added to group redis<\/code> to grant read and write permissions to the socket.<\/p>\n
    2. Configuration in wp-config.php<\/h3>\n
    To ensure that the Redis Object Cache plugin in WordPress connects correctly via a Unix socket, add the following directives to the site's configuration file:<\/p>\n
    \/\/ Configure Redis connection via Unix Socket define('WP_REDIS_SCHEME', 'unix'); define('WP_REDIS_PATH', '\/var\/run\/redis\/redis-server.sock'); define('WP_REDIS_DATABASE', 0); \/\/ Redis database index<\/code><\/pre>\n
    Memory Management: maxmemory and Eviction Policies<\/h2>\n
    If Redis runs out of allocated RAM without a clearly defined eviction policy, it will start returning out of data errors (OOM command not allowed). According to Redis documentation on key displacement<\/a>, for WordPress and WooCommerce it is critical to set it up correctly maxmemory-policy<\/code>.<\/p>\n
    Recommended configurations in redis.conf:<\/h3>\n
    maxmemory 512mb # Allocated amount depending on server RAM maxmemory-policy allkeys-lru<\/code><\/pre>\n