Maxim Mironjuk
-
May 03, 2026
In heavily trafficked Magento shops, every PHP-FPM worker on a server accesses the same handful of frequently read configuration values, such as store configuration, feature flags, or layout handle mappings, which rarely change per request but get read fresh from Redis on every single request anyway. Such extremely frequently read keys are called hot keys, and even with a fundamentally performant Redis, they can become a measurable bottleneck under high load, because every single network round trip to Redis costs time that adds up noticeably across tens of thousands of requests per minute. Redis client-side caching over the RESP3 protocol promises relief here by holding hot-key values directly in the calling process's own memory, with clear but practically relevant limits for integrating it into Magento's cache backend architecture.