From 52529c34f597ee2118f9979d331726648b25e295 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Fri, 16 Oct 2020 18:49:57 +0200 Subject: [PATCH 01/21] Update config-redis.md add quick explanation how to setup Redis --- .../v2.3/config-guide/redis/config-redis.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 685f8e91ea1..2fd86a4adf6 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -27,6 +27,31 @@ Installing and configuring the Redis software is beyond the scope of this guide. * [digitalocean](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-redis) * [Redis documentation page](http://redis.io/documentation) +## Set up redis configuration + +Depending on your installation, you can usually find your Redis configuration at /etc/redis/redis.conf or /etc/redis/`port`.conf + +To optimize your Redis instance to your needs, you get best results when using a dedicated instance for each sessions, Magento cache and FPC. + +For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. +You can get the details advantages and disadvantages on the [Redis Persistence documentation](https://redis.io/topics/persistence). + +For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). + +For performance tuning you can also enable these settings for asynchronous deletion. This will not change the behavior of Redis (see also [redis news](http://antirez.com/news/93). + +``` +lazyfree-lazy-eviction yes +lazyfree-lazy-expire yes +lazyfree-lazy-server-del yes +replica-lazy-flush yes +``` +From redis 6.x onwards, you can also set + +``` +lazyfree-lazy-user-del yes +``` + ## For more information You can find more information about configuring Redis from the following: From fd42dbafea0e387636aff037f78d564b7a189b9a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Fri, 16 Oct 2020 18:58:02 +0200 Subject: [PATCH 02/21] Update config-redis.md Fix line length --- src/guides/v2.3/config-guide/redis/config-redis.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 2fd86a4adf6..b84446798d1 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -16,7 +16,8 @@ Redis features include: * Redis supports on-disk save and master/slave replication. {:.bs-callout-info} -Starting in Magento 2.0.6, you can use either Redis or [memcached]({{ page.baseurl }}/config-guide/memcache/memcache.html) for session storage. Earlier issues with the Redis session handler and session locking have been resolved. +Starting in Magento 2.0.6, you can use either Redis or [memcached]({{ page.baseurl }}/config-guide/memcache/memcache.html) for session storage. Earlier issues +with the Redis session handler and session locking have been resolved. ## Install Redis {#config-redis-install} @@ -27,7 +28,7 @@ Installing and configuring the Redis software is beyond the scope of this guide. * [digitalocean](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-redis) * [Redis documentation page](http://redis.io/documentation) -## Set up redis configuration +## Set up redis configuration {#config-redis-setup} Depending on your installation, you can usually find your Redis configuration at /etc/redis/redis.conf or /etc/redis/`port`.conf @@ -36,9 +37,12 @@ To optimize your Redis instance to your needs, you get best results when using a For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. You can get the details advantages and disadvantages on the [Redis Persistence documentation](https://redis.io/topics/persistence). -For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). +For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. +The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of +magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). -For performance tuning you can also enable these settings for asynchronous deletion. This will not change the behavior of Redis (see also [redis news](http://antirez.com/news/93). +For performance tuning you can also enable these settings for asynchronous deletion. This will not change the behavior of Redis (see also +[redis news](http://antirez.com/news/93). ``` lazyfree-lazy-eviction yes From d4a4ec0bbaf8283d309eaf13e9dfed85d0fcde15 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Fri, 16 Oct 2020 19:01:46 +0200 Subject: [PATCH 03/21] Update config-redis.md fix markdown --- src/guides/v2.3/config-guide/redis/config-redis.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index b84446798d1..42cbf6073be 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -37,14 +37,14 @@ To optimize your Redis instance to your needs, you get best results when using a For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. You can get the details advantages and disadvantages on the [Redis Persistence documentation](https://redis.io/topics/persistence). -For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. +For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). For performance tuning you can also enable these settings for asynchronous deletion. This will not change the behavior of Redis (see also [redis news](http://antirez.com/news/93). -``` +```ini lazyfree-lazy-eviction yes lazyfree-lazy-expire yes lazyfree-lazy-server-del yes @@ -52,7 +52,7 @@ replica-lazy-flush yes ``` From redis 6.x onwards, you can also set -``` +```ini lazyfree-lazy-user-del yes ``` From 766ee99bf4b201cded23052ff53bd53a8d90b5db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Mon, 19 Oct 2020 13:25:04 +0200 Subject: [PATCH 04/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Barny Shergold --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 42cbf6073be..aa1a26e0c40 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -35,7 +35,7 @@ Depending on your installation, you can usually find your Redis configuration at To optimize your Redis instance to your needs, you get best results when using a dedicated instance for each sessions, Magento cache and FPC. For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. -You can get the details advantages and disadvantages on the [Redis Persistence documentation](https://redis.io/topics/persistence). +You can get details of the advantages and disadvantages of RDB and AOF on the [Redis Persistence documentation](https://redis.io/topics/persistence). For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of From fcd1378974b4a9321e40f3f782a5f729e640a5c9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Mon, 19 Oct 2020 13:25:17 +0200 Subject: [PATCH 05/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Barny Shergold --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index aa1a26e0c40..e8217956169 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -37,7 +37,7 @@ To optimize your Redis instance to your needs, you get best results when using a For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. You can get details of the advantages and disadvantages of RDB and AOF on the [Redis Persistence documentation](https://redis.io/topics/persistence). -For the cache instance, you should make sure, the instance is set up big enough to store your whole Magento cache in it. +For the cache instance, you should make sure the instance is set up to be large enough to store your whole Magento cache. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). From e99dafa2c8f723ba388c0e6e4c1e2986a925d987 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Mon, 19 Oct 2020 13:35:45 +0200 Subject: [PATCH 06/21] Update config-redis.md Add more explanation about AOF and RDB --- src/guides/v2.3/config-guide/redis/config-redis.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index e8217956169..4fd1fb8bb92 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -37,6 +37,13 @@ To optimize your Redis instance to your needs, you get best results when using a For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. You can get details of the advantages and disadvantages of RDB and AOF on the [Redis Persistence documentation](https://redis.io/topics/persistence). +RDB (Redis Database File) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. +This can be configured with the `save` setting inside `redis.conf`. + +AOF (Append Only File) stores each write operation send to redis in a journal file. This file ẃill be read by Redis on restart to restore the the original dataset. + +It's possible, to enable both RDB ands AOF the same time. + For the cache instance, you should make sure the instance is set up to be large enough to store your whole Magento cache. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). From 1867be1ea3dfff59263b6a0150c74d28a5c1a07c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Mon, 19 Oct 2020 14:45:45 +0200 Subject: [PATCH 07/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Barny Shergold --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 4fd1fb8bb92..8facd349cd7 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -40,7 +40,7 @@ You can get details of the advantages and disadvantages of RDB and AOF on the [R RDB (Redis Database File) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. This can be configured with the `save` setting inside `redis.conf`. -AOF (Append Only File) stores each write operation send to redis in a journal file. This file ẃill be read by Redis on restart to restore the the original dataset. +AOF (Append Only File) stores each write operation sent to Redis in a journal file. This file ẃill be read by Redis on restart to restore the original dataset. It's possible, to enable both RDB ands AOF the same time. From 791b0baf708da9196b83564a573d857259499e21 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Mon, 19 Oct 2020 14:45:52 +0200 Subject: [PATCH 08/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Barny Shergold --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 8facd349cd7..9d73f9caaa3 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -42,7 +42,7 @@ This can be configured with the `save` setting inside `redis.conf`. AOF (Append Only File) stores each write operation sent to Redis in a journal file. This file ẃill be read by Redis on restart to restore the original dataset. -It's possible, to enable both RDB ands AOF the same time. +It's possible to enable both RDB and AOF at the same time. For the cache instance, you should make sure the instance is set up to be large enough to store your whole Magento cache. The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of From 3cf0e3b90f177ab1ae8d63d144a06722953cd709 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Mon, 19 Oct 2020 16:04:19 +0200 Subject: [PATCH 09/21] Update config-redis.md RDB written out correctly --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 9d73f9caaa3..a9e0c2c2b3a 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -37,7 +37,7 @@ To optimize your Redis instance to your needs, you get best results when using a For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. You can get details of the advantages and disadvantages of RDB and AOF on the [Redis Persistence documentation](https://redis.io/topics/persistence). -RDB (Redis Database File) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. +RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. This can be configured with the `save` setting inside `redis.conf`. AOF (Append Only File) stores each write operation sent to Redis in a journal file. This file ẃill be read by Redis on restart to restore the original dataset. From 8b4ff9c073103147aa474d0a82c9c6bdc531b176 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:19:13 +0200 Subject: [PATCH 10/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Margaret Eker --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index a9e0c2c2b3a..6feced73e38 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -16,7 +16,7 @@ Redis features include: * Redis supports on-disk save and master/slave replication. {:.bs-callout-info} -Starting in Magento 2.0.6, you can use either Redis or [memcached]({{ page.baseurl }}/config-guide/memcache/memcache.html) for session storage. Earlier issues +Starting from Magento 2.0.6, you can use either Redis or [memcached]({{ page.baseurl }}/config-guide/memcache/memcache.html) for session storage. Earlier issues with the Redis session handler and session locking have been resolved. ## Install Redis {#config-redis-install} From 5a280ed679738c9175cafe6971da73d4cf7abe7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:19:21 +0200 Subject: [PATCH 11/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Margaret Eker --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 6feced73e38..246c07bffeb 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -57,7 +57,7 @@ lazyfree-lazy-expire yes lazyfree-lazy-server-del yes replica-lazy-flush yes ``` -From redis 6.x onwards, you can also set +On Redis 6.x and later, you can also add the following value: ```ini lazyfree-lazy-user-del yes From 50d9c193b3e4b4181721455b0b9b9557a83adc7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:23:10 +0200 Subject: [PATCH 12/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Margaret Eker --- src/guides/v2.3/config-guide/redis/config-redis.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 246c07bffeb..b72dab1dedd 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -44,11 +44,10 @@ AOF (Append Only File) stores each write operation sent to Redis in a journal fi It's possible to enable both RDB and AOF at the same time. -For the cache instance, you should make sure the instance is set up to be large enough to store your whole Magento cache. -The required size depends on different factors (like number of products and store views) but the required size of the file system cache gives you the order of -magnitude. Persistence is not required here as the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). +For the cache instance, set up the instance so that it is large enough to store your entire Magento cache. +Size requirements depend on different factors like the number of products and store views, but the size requirement for the the file system cache gives you the order of magnitude. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). -For performance tuning you can also enable these settings for asynchronous deletion. This will not change the behavior of Redis (see also +For performance tuning, you can also enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis. [redis news](http://antirez.com/news/93). ```ini From 36f53ecb3ad6efab62b8d0dbb3d33094890dabf7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:24:50 +0200 Subject: [PATCH 13/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Margaret Eker --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index b72dab1dedd..26632cf697e 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -32,7 +32,7 @@ Installing and configuring the Redis software is beyond the scope of this guide. Depending on your installation, you can usually find your Redis configuration at /etc/redis/redis.conf or /etc/redis/`port`.conf -To optimize your Redis instance to your needs, you get best results when using a dedicated instance for each sessions, Magento cache and FPC. +To optimize the Redis instance for your requirements, you get best results by using a dedicated instance for each session, Magento cache and FPC. For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. You can get details of the advantages and disadvantages of RDB and AOF on the [Redis Persistence documentation](https://redis.io/topics/persistence). From cd1f4b8e3f65c9593de4f54c808d4d3b944b058a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:26:06 +0200 Subject: [PATCH 14/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Margaret Eker --- src/guides/v2.3/config-guide/redis/config-redis.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 26632cf697e..d4b41aeb4fc 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -34,15 +34,13 @@ Depending on your installation, you can usually find your Redis configuration at To optimize the Redis instance for your requirements, you get best results by using a dedicated instance for each session, Magento cache and FPC. -For sessions, it's recommended to enable persistence. This can either be done by regular RDB snapshots or by using the AOF persistence logs. -You can get details of the advantages and disadvantages of RDB and AOF on the [Redis Persistence documentation](https://redis.io/topics/persistence). +For sessions, we recommend that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database Backup (RDB) snapshots, or Append Only File (AOF) persistence logs. -RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. -This can be configured with the `save` setting inside `redis.conf`. +- RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. Use the `save` setting inside the `redis.conf` file to configure this setting. -AOF (Append Only File) stores each write operation sent to Redis in a journal file. This file ẃill be read by Redis on restart to restore the original dataset. +- AOF (Append Only File) stores each write operation sent to Redis in a journal file. Redis reads this file on restart only and uses it to restore the original dataset. -It's possible to enable both RDB and AOF at the same time. +You can also enable both the RDB and AOF options at the same time. For additional details including the advantages and disadvantages of the persistence options, see the [Redis Persistence documentation](https://redis.io/topics/persistence). For the cache instance, set up the instance so that it is large enough to store your entire Magento cache. Size requirements depend on different factors like the number of products and store views, but the size requirement for the the file system cache gives you the order of magnitude. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). From 46a4cd463feef8d9323bcddb1fc9789b3805a02b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:28:56 +0200 Subject: [PATCH 15/21] Update config-redis.md --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index d4b41aeb4fc..87ecd8430e5 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -30,7 +30,7 @@ Installing and configuring the Redis software is beyond the scope of this guide. ## Set up redis configuration {#config-redis-setup} -Depending on your installation, you can usually find your Redis configuration at /etc/redis/redis.conf or /etc/redis/`port`.conf +Depending on your installation, you can usually find your Redis configuration in one of the following files: `/etc/redis/redis.conf` or `/etc/redis/.conf` To optimize the Redis instance for your requirements, you get best results by using a dedicated instance for each session, Magento cache and FPC. From fd21464ca8e70dce0c3748118056a57fdf6e3ad9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:30:58 +0200 Subject: [PATCH 16/21] Update config-redis.md --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 87ecd8430e5..dee71a245a9 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -46,7 +46,7 @@ For the cache instance, set up the instance so that it is large enough to store Size requirements depend on different factors like the number of products and store views, but the size requirement for the the file system cache gives you the order of magnitude. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). For performance tuning, you can also enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis. -[redis news](http://antirez.com/news/93). +See also [redis news](http://antirez.com/news/93) for details about asynchronous deletion. ```ini lazyfree-lazy-eviction yes From 96d09a6ce4ec785fa087674650b618f79dbcdb2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:34:24 +0200 Subject: [PATCH 17/21] Update config-redis.md fix markdown list --- src/guides/v2.3/config-guide/redis/config-redis.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index dee71a245a9..0344bb48a6c 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -34,11 +34,14 @@ Depending on your installation, you can usually find your Redis configuration in To optimize the Redis instance for your requirements, you get best results by using a dedicated instance for each session, Magento cache and FPC. -For sessions, we recommend that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database Backup (RDB) snapshots, or Append Only File (AOF) persistence logs. +For sessions, we recommend that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database +Backup (RDB) snapshots, or Append Only File (AOF) persistence logs. -- RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. Use the `save` setting inside the `redis.conf` file to configure this setting. +* RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the +last save. Use the `save` setting inside the `redis.conf` file to configure this setting. -- AOF (Append Only File) stores each write operation sent to Redis in a journal file. Redis reads this file on restart only and uses it to restore the original dataset. +* AOF (Append Only File) stores each write operation sent to Redis in a journal file. Redis reads this file on restart only and uses it to restore the +original dataset. You can also enable both the RDB and AOF options at the same time. For additional details including the advantages and disadvantages of the persistence options, see the [Redis Persistence documentation](https://redis.io/topics/persistence). From c79a29a1011865e1104f95c3a2df441e3366f016 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:43:28 +0200 Subject: [PATCH 18/21] Update config-redis.md --- src/guides/v2.3/config-guide/redis/config-redis.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 0344bb48a6c..a89412d6749 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -37,11 +37,9 @@ To optimize the Redis instance for your requirements, you get best results by us For sessions, we recommend that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database Backup (RDB) snapshots, or Append Only File (AOF) persistence logs. -* RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the -last save. Use the `save` setting inside the `redis.conf` file to configure this setting. +* RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. Use the `save` setting inside the `redis.conf` file to configure this setting. -* AOF (Append Only File) stores each write operation sent to Redis in a journal file. Redis reads this file on restart only and uses it to restore the -original dataset. +* AOF (Append Only File) stores each write operation sent to Redis in a journal file. Redis reads this file on restart only and uses it to restore the original dataset. You can also enable both the RDB and AOF options at the same time. For additional details including the advantages and disadvantages of the persistence options, see the [Redis Persistence documentation](https://redis.io/topics/persistence). From 82922ea7125a3d277244fc1ad139af0a8ed45fd9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 20:47:45 +0200 Subject: [PATCH 19/21] Update config-redis.md --- src/guides/v2.3/config-guide/redis/config-redis.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index a89412d6749..d9f1d79a19c 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -16,8 +16,7 @@ Redis features include: * Redis supports on-disk save and master/slave replication. {:.bs-callout-info} -Starting from Magento 2.0.6, you can use either Redis or [memcached]({{ page.baseurl }}/config-guide/memcache/memcache.html) for session storage. Earlier issues -with the Redis session handler and session locking have been resolved. +Starting from Magento 2.0.6, you can use either Redis or [memcached]({{ page.baseurl }}/config-guide/memcache/memcache.html) for session storage. Earlier issues with the Redis session handler and session locking have been resolved. ## Install Redis {#config-redis-install} @@ -34,8 +33,7 @@ Depending on your installation, you can usually find your Redis configuration in To optimize the Redis instance for your requirements, you get best results by using a dedicated instance for each session, Magento cache and FPC. -For sessions, we recommend that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database -Backup (RDB) snapshots, or Append Only File (AOF) persistence logs. +For sessions, we recommend that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database Backup (RDB) snapshots, or Append Only File (AOF) persistence logs. * RDB (Redis Database Backup) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. Use the `save` setting inside the `redis.conf` file to configure this setting. @@ -46,8 +44,7 @@ You can also enable both the RDB and AOF options at the same time. For additiona For the cache instance, set up the instance so that it is large enough to store your entire Magento cache. Size requirements depend on different factors like the number of products and store views, but the size requirement for the the file system cache gives you the order of magnitude. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). -For performance tuning, you can also enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis. -See also [redis news](http://antirez.com/news/93) for details about asynchronous deletion. +For performance tuning, you can also enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis. See also [redis news](http://antirez.com/news/93) for details about asynchronous deletion. ```ini lazyfree-lazy-eviction yes From 153c1942d7b56ed2623c78d6e8fcd59a08ca001d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 21:31:21 +0200 Subject: [PATCH 20/21] Update config-redis.md Reformulated size explanation in config-redis.md to be more clear --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index d9f1d79a19c..1e1db2f839a 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -42,7 +42,7 @@ For sessions, we recommend that you enable persistence to copy Redis data to dis You can also enable both the RDB and AOF options at the same time. For additional details including the advantages and disadvantages of the persistence options, see the [Redis Persistence documentation](https://redis.io/topics/persistence). For the cache instance, set up the instance so that it is large enough to store your entire Magento cache. -Size requirements depend on different factors like the number of products and store views, but the size requirement for the the file system cache gives you the order of magnitude. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). +Size requirements depend on different factors like the number of products and store views. When you have your Magento Cache previously put into your file system, you can check out the size of the cache folder for a good starting point to set up your Redis instance. For example, when you have a 5 GB 'var/cache' folder your Redis instance should have a similar size available. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). For performance tuning, you can also enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis. See also [redis news](http://antirez.com/news/93) for details about asynchronous deletion. From 324d97b23a8202ff833c8cdc2be679011862fb55 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20H=C3=BCnig?= Date: Tue, 20 Oct 2020 21:38:54 +0200 Subject: [PATCH 21/21] Update src/guides/v2.3/config-guide/redis/config-redis.md Co-authored-by: Margaret Eker --- src/guides/v2.3/config-guide/redis/config-redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/v2.3/config-guide/redis/config-redis.md b/src/guides/v2.3/config-guide/redis/config-redis.md index 1e1db2f839a..3d0b4e89398 100644 --- a/src/guides/v2.3/config-guide/redis/config-redis.md +++ b/src/guides/v2.3/config-guide/redis/config-redis.md @@ -42,7 +42,7 @@ For sessions, we recommend that you enable persistence to copy Redis data to dis You can also enable both the RDB and AOF options at the same time. For additional details including the advantages and disadvantages of the persistence options, see the [Redis Persistence documentation](https://redis.io/topics/persistence). For the cache instance, set up the instance so that it is large enough to store your entire Magento cache. -Size requirements depend on different factors like the number of products and store views. When you have your Magento Cache previously put into your file system, you can check out the size of the cache folder for a good starting point to set up your Redis instance. For example, when you have a 5 GB 'var/cache' folder your Redis instance should have a similar size available. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). +Size requirements depend on different factors like the number of products and store views. As a starting point, you can use the size of the cache folder on your file system. For example, if the `var/cache` folder on your file system is 5 GB, set up your Redis instance with at least 5 GB to start. Persistence is not required for the cache instance because the Magento cache can be restored. See also [Redis cache guide](https://redis.io/topics/lru-cache). For performance tuning, you can also enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis. See also [redis news](http://antirez.com/news/93) for details about asynchronous deletion.