Shopware performance
Shopware Redis setup: cache, sessions and locks in memory
We set up Redis for Shopware 6: for cache, sessions, locks and counters, cleanly separated and configured to stay stable under load.
- since 2012
- 200+ online shops
- 800+ websites
- Shopware Partner since 2014
Online shops
200+
delivered since 2012
Projects delivered
1000+
since 2012
Shopware Partner
since 2014
own plugins in the Shopware Store
-
Shopware Partner since 2014
-
Mollie Partner since 2021
-
Trusted Shops Partner
-
eRecht24 Partner
-
magnalister Partner since 2022
-
Base Partner since 2026
-
sync4 Partner since 2022
-
Pickware Partner since 2019
-
ADCELL Partner
Why Shopware stalls under load without Redis
Without Redis, Shopware stores cache and sessions in the file system or the database. With several servers or many simultaneous visitors this becomes slow and error-prone: caches drift apart, baskets get lost and the database is given work it should not have to do.
What a Shopware Redis setup does for you
- Cache and sessions sit in memory and can be accessed quickly.
- Several app servers share the same cache and the same sessions.
- The database is relieved of locks and counters.
- Separate Redis databases prevent a cache clear from deleting sessions.
Scope of services
What we take on for your Shopware Redis setup
- App and HTTP cache
Shopware stores its caches in Redis instead of the file system.
- Sessions & baskets
Customer sessions are preserved even behind several servers.
- Locks & counters
Locks and increments run in Redis and take load off MySQL.
- Clean separation
Dedicated databases for each purpose, so a cache clear deletes nothing important.
- Memory & eviction
Memory limits and eviction rules to suit your catalogue.
- Measurement
Response times before and after, so the effect is proven.
With Redis, Shopware 6 stores cache, sessions, locks and counters in memory instead of in the file system or the database. This makes repeat page views faster and keeps baskets stable even behind several servers. We set up Redis to suit your hosting, separate the purposes cleanly and measure what it achieves.
Tech stack
- ApplicationShopware, Laravel or WordPress with theme and plugins
- Cache and searchRedis and Elasticsearch configured to fit
- PHPcurrent version with OPcache
- Serverour own servers with NVMe storage
Where Redis comes in with Shopware
Shopware has several places where Redis can help: the app cache, the HTTP cache, storage of sessions and baskets, and locks and counters that would otherwise end up in the database. Not every one of them pays off in every shop. We use measurements to check which layers carry the most load in your shop and set up exactly those.
public static function getSubscribedEvents(): array
{
return [
ProductPageLoadedEvent::class => 'onProductPage',
];
}
public function onProductPage(ProductPageLoadedEvent $event): void
{ /* add data without touching the core */ } Configuration that holds up under load
Redis is fast as long as it has enough memory and the rules are right. We define memory limits and eviction rules, decide which data needs to be persisted and keep cache and sessions in separate databases. How Redis works together with the rest of the cache is described on the page on cache optimisation.
Search result
Examplewww.web-labels.de › en › shopware › redis
Setting up Redis for Shopware 6 | Web Labels
Redis for Shopware 6: we set up Redis for app cache, HTTP cache, sessions, locks and counters, separate the databases cleanly and measure the effect.
How we work
How we bring Redis into your Shopware shop
- Understand
We look at your business, your systems and your figures before we suggest anything.
- Plan
You receive a concept and a quote with individual items and a realistic schedule.
- Build
We develop in stages. You see interim results on a test environment and approve them.
- Run
After go-live we take care of hosting, updates and monitoring if you want us to.
Your contacts
Your contacts for Redis and Shopware
Tell us where your project stands. Janis and Tim will listen, ask questions and tell you honestly what we recommend and roughly what it will cost.
Our team for your questions
-
René Grosche Managing Director
-
Marco Kreutzfeldt Deputy Managing Director · Back office
-
Tim Schröder Key Account Manager · Consulting and quotes
-
Janis Rittmeier Key Account Manager · Consulting and quotes
-
Lennart Albrecht Head of Development
-
Tom Baustian Web design · Performance marketing · Audio
-
Tajara-Tabea Leonard Web design · Content · SEO
-
Ken Raupach Web design · Performance marketing
-
Muhammed Tay Web development
-
Alexander Folz Web development
-
Aaron Griem Web development
-
Leon Fischer Web development
-
Patrick Heidl Web development
-
Tobias Schäfer Web development · Complex development
-
Laura Schop Web development
- Aleksej Werestschagin Web development
-
Julina Sievert Apprentice
-
Rosa-Lee Biesterfeldt Apprentice
Frequently asked questions about Shopware Redis
All questions and answersWhich parts of Shopware can use Redis?
Shopware 6 can use Redis for the app cache, the HTTP cache, sessions, baskets, locks and counters, among other things. Which parts make sense depends on your setup and the Shopware version.
Why should cache and sessions be kept separate?
If both are in the same Redis database, clearing the cache also deletes the sessions. Customers would then be logged out and their baskets empty. That is why we separate the purposes.
Does Redis need its own server?
Not necessarily. In smaller shops Redis often runs on the same server. With several app servers or high load, a separate instance is usually the better choice.
- Performance
Faster Shopware 6 shops: we measure with ShopSignal and Tideways, find the bottlenecks in database, cache, search, theme and server, and fix what makes the biggest difference first.
- Elasticsearch
We connect Elasticsearch or OpenSearch to Shopware 6 so that search, filters and listings come from a dedicated index and the database is relieved.
- Database queries
We find the queries that slow down your Shopware shop, understand them with EXPLAIN and profiling, and fix them with indexes, better DAL queries or adjusted plugin code.
- Database performance
We configure MySQL or MariaDB to suit your Shopware shop, clean up growing tables and make sure background processes do not slow the database down.
A few sentences are enough to start. We will get back to you with questions or a suggested date.