There are several caches in shopware which can be used to optimize the performance. This page gives a brief overview and shows how to configure them.
Overview
The HTTP Cache is a must have for every production system. With enabled cache the performance of the shop can be greatly increased.
How to configure the http cache
The HTTP cache configuration takes place completely in the .env file. The following configurations are available here:
Name
Description
SHOPWARE_HTTP_CACHE_ENABLED
Enables the http cache
SHOPWARE_HTTP_DEFAULT_TTL
Defines the default cache time
How to trigger the http cache warmer
To warm up the HTTP cache you can simply use the console command http:cache:warm:up. This command sends a message to the message queue for each sales channel domain to warm it up as fast as possible. It is important that queue workers are started according to our message queue.
How to change the cache storage
The standard shopware http cache can be exchanged or reconfigured in several ways. The standard cache comes with an adapter.filesystem. The configuration can be found in the platform/src/Core/Framework/Resources/config/packages/framework.yaml file.
1
framework:
2
cache:
3
pools:
4
cache.http:
5
adapter: cache.adapter.filesystem
6
tags:true
Copied!
This is a Symfony cache pool configuration and therefore supports all adapters from the Symfony FrameworkBundle.
App Cache
The app cache defines the default cache adapter for shopware. As you can see in this default configuration every cache-pool in shopware uses the adapter defined in the app cache as default:
1
framework:
2
cache:
3
prefix_seed:"%kernel.cache.hash%"
4
app: cache.adapter.filesystem
5
pools:
6
cache.object:
7
default_lifetime:3600
8
adapter: cache.app
9
tags: cache.tags
10
cache.http:
11
default_lifetime:3600
12
adapter: cache.app
13
tags: cache.tags
14
cache.tags:
15
adapter: cache.app
Copied!
This is also a Symfony cache configuration and therefore supports all adapters from the Symfony FrameworkBundle.
Object Cache
The object cache pool is used for the caching of the data abstraction layer in shopware and can be configured like any other pool.
Example: Replace some cache with Redis
"Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker." In this example we change the default HTTP cache adapter to redis. It is possible to change every adapter like in this example. A running redis instance is required for this to work. he configuration can be overridden by creating/editing the file framework.yaml
1
# config/packages/framework.yaml
2
framework:
3
cache:
4
default_redis_provider:'redis://host:port'
5
pools:
6
cache.http:
7
default_lifetime:3600
8
adapter: cache.adapter.redis
9
tags: cache.tags
Copied!
Replace the host and port with your redis instance. It is also possible to change the cache adapter for app which would affect every pool, since they inherit from app by default:
1
framework:
2
cache:
3
app: cache.adapter.redis
4
default_redis_provider:'redis://host:port'
Copied!
Twig Cache
Twig caches all compiled template files by default. With the cache option a directory can be defined, where twig saves the compiled templates. This path can be overridden by creating/editing a twig.yaml:
1
# config/packages/twig.yaml
2
twig:
3
cache:'%kernel.cache_dir%/twig'
Copied!
If you want to know more about caching in twig, take a look at the Twig for Developers page in the twig documentation.