Increased page load time with 2.3.4

[monotheist]

Preconditions (*)

1. Magento 2.3.4
2. Varnish
3. Redis

Steps to reproduce (*)

1. Upgrade from 2.3.3 to 2.3.4

Expected result (*)

1. Page load either match the previous version or better

Actual result (*)

1. Product page load is around 2700 ms while 2.3.3 delivers at 800 to 1000 ms

[magento-deployment-service]

Thanks for opening this issue!

[m2-assistant]

Hi @monotheist. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@monotheist do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[devchris79]

You might want to check the cache is enabled, Composer does disable it following an upgrade. I think this is due to be fixed though.

To check cache status:

bin/magento cache:status

To enable cache:

bin/magento cache:enable

[devchris79]

Sorry, looks like it should be fixed in 2.3.4 #24892

[monotheist]

Cache is enabled. I have also tested this in atleast 3 development instances.

[TimQSO]

When you enable the profiler, you can see where the processing time goes to:

bin/magento dev:profiler:enable

[kurtdeserter]

I can confirm performance issues with 2.3.4 and cache enabled.

[palviggi-flagbit]

We had the same problem, and at least on our case we tracked it down to a high amount of "show table status like 'store';" queries, resulting from the fix in #24959

it adds a constant check to see if the store tables exists, without caching, even in the same transaction.

I reverted the changes and load went back to normal

[alex9434]

+1 I can also confirm that I experienced the same issue with 3x load times after upgrade to 2.3.4. Is there any hotfix to solve this? The system has become almost unusable. Cache is enabled.

[alex9434]

Dear @palviggi-flagbit,
can you tell me how you did revert back the changes from the fix in #24959. I would like to do the same to reduce load times back to the previous status.
Thank you,
alex

[palviggi-flagbit]

Dear @palviggi-flagbit,
can you tell me how you did revert back the changes from the fix in #24959. I would like to do the same to reduce load times back to the previous status.
Thank you,
alex

I copied the function code from the previous tag available for each file (for example https://github.com/ivan-koliadynskyy/magento2/blob/2.3.2/app/code/Magento/Store/App/Config/Source/RuntimeConfigSource.php).

Last week we learned that in our case the main problem was that our hosting service had a peculiar filesystem setup on the databases that made "SHOW STATUS" queries take 60x longer than usual, and they knew about it but didn't tell us until we raised the problem.
But you have to test it to see if it's really a fix for you. Best way is to profile your website, our profiling lead to this particular query/PR

[alex9434]

I copied the function code from the previous tag available for each file (for example https://github.com/ivan-koliadynskyy/magento2/blob/2.3.2/app/code/Magento/Store/App/Config/Source/RuntimeConfigSource.php).

Last week we learned that in our case the main problem was that our hosting service had a peculiar filesystem setup on the databases that made "SHOW STATUS" queries take 60x longer than usual, and they knew about it but didn't tell us until we raised the problem.
But you have to test it to see if it's really a fix for you. Best way is to profile your website, our profiling lead to this particular query/PR

I can confirm that this solved the problem for me! So it seems to be the fix in #24959 that caused these issues.

You mentioned that your hosting service hat a particular setup that made "SHOW STATUS" slow. I have a Percona Mysql on EXT4 on a SSD. Is that similar to your setup?