QuestionQ43

VerifiedConfigure and Deploy

An Architect is setting the preload_keys for Redis on an Adobe Commerce on-premise instance.

The Architect finds that these cache keys are loaded on every frontend request: EAV_ENTITY_TYPES, GLOBAL_PLUGIN_LIST, DB_IS_UP_TO_DATE, SYSTEM_DEFAULT.

  • The id_prefix for frontend => page_cache is set to 063_.
  • The id_prefix for frontend => default is set to 162_.
  • The Architect has enabled and configured Redis L2 caching.

How should preload_keys be configured?

Explanation

The listed keys belong to the default cache frontend, so each preload key must use its 162_ id_prefix. With Redis L2 caching, Commerce preloads the remote cache data-version hashes rather than the data itself; each preload key must therefore end in :hash.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!