bmsetr.blogg.se - Magento 2 set private cache

#Magento 2 set private cache professional

PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 45056 bytes) in Unknown on line 0, referer: PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/vendor/magento/framework/Serialize/Serializer/Json.php on line 42, referer: PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 32768 bytes) in Unknown on line 0 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 20480 bytes) in /var/2020] PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 40960 bytes) in Unknown on line 0, referer: PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/vendor/magento/framework/Serialize/Serializer/Json.php on line 42 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 65536 bytes) in Unknown on line 0 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 4096 bytes) in /var/www/html/vendor/magento/module-csp/Model/BlockCache.php on line 78 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 122880 bytes) in Unknown on line 0 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/vendor/magento/module-csp/Model/BlockCache.php on line 108 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 48238592 bytes) in /var/www/html/vendor/magento/framework/Serialize/Serializer/Json.php on line 24 I copied the log errors from another user running into the same issue:

The log errors show that this function is causing issues. Quick workaround is disabling the module to keep the shop RAM usage healthy. This function uses a crazy amound of RAM. Vendor/magento/module-csp/Model/BlockCache.php The result would get cached and stay in the cache until the redis cache was cleared.Īfter a lot of digging I found the source of the issue in: We found out via SSH top that the RAM consumption was peaking during the category generation on the frontend (from uncachd to cached).įirst we thought it was a Redis issue because 9 out of ten times the page would look broken like we have seen in the M1 days because of a Redis issue.īut actually "the broken page layout" was the result of PHP running out of memory.

#Magento 2 set private cache professional

Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.

Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.

Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.

Severity: S0 - Affects critical data or functionality and leaves users without workaround.

This information will help during Confirmation and Issue triage processes.

Please provide Severity assessment for the Issue as Reporter.

Sometimes the OOM killer was triggered that would sacrifice the Elasticsearch etc.

The actual result is that maybe 12 categories would open ok but around 2 or 3 would look completely broken with broken styling or even a 500 server error.

The expected result is that all 15 categories would open one by one and look ok.

Search a couple of times and wait for the result.

Open a dropdown with categories and click them open in a new tab one by one.

Clear all caches and also redis-cli flushall.

Have around 2000+ products in multiple categories.

8gb to 10gb of VPS ram with Magento having 2gb assigned.

Redis enabled for FPC and backend cache.