Too many DB queries for _conditions table when...

Hello!
I would like to ask for advice/help with the following problem:
After installing AMM on pure J4, the number of queries to the DB is multiplied by about 4x, but on the production site (updated J3 to J4) with articles and modules, queries take 4-5 seconds! and only then the content is displayed.
Approximately 6,000 queries are made to the database to display a page with 10 modules. Most of the questions are about tables:
_conditions*
_modules

The same page (with AMM used) on J3 needs about 250 queries to display.

Please do you know what is causing this problem and how to fix it?
Thank you in advance for your reply,
Peter

Hi,
Thank you for your response. Unfortunately, the website is not accessible from the world. I have to wait for the DNS to be made available/set up and that won't be possible until Monday.
For now I can send query/sql_log for download:

Thank you, Peter

Thank you, Peter

Hi

I can confirm that this is an issue.

J3 site with AMM has ~300 queries on the homepage.

Migrating to J4 ups this to 4200. Disabling AMM drops back to about 300.

In our testing it looks like AMM is querying all modules on every page. Meaning as your usage of modules grows, site-wide performance gets progressively worse.

I've tested this by creating a fresh J4 install with AMM. Standard out the box config. Adding modules and using menu item assignments on other pages increases queries on the homepage. We added 10 modules to other pages, with the same condition, and it added 30 queries to the homepage.

Disabling AMM drops this by about 100 queries. Core joomla module manager is not checking every module per page so I hope that AMM can be updated to behave in a more performant fashion.

Otherwise this makes AMM impossible to use for medium+ sized websites. We are seeing negative performance implications on the J3 and 4 versions of the site in question using AMM.

Please advise.

Hi Peter

Thanks for the speedy response. Core Joomla module manager does not check every module on every page. While I appreciate you're saying it shouldn't generate so many queries, it's still a long term performance issue. Some of our websites have 600-1000 modules and so unless this can be improved, we're going to have to stop using AMM as we transition to J4.

I understand why it needs to check every module if there isn't a menu item assignment set. Unfortunately we've proved that even with menu item assignment, AMM checks every module for every page - which seems unnecessary since core joomla doesn't do this.

For the 4200 queries issue, please see your access information below. We have left debugging on so you can see the query trace at end of page.

Morning Peter

Thanks for this, but unfortunately this does not help.

To address the 4200 queries - we used your migration process to upgrade from AMM 7 to 9 (for the J4 migration). It's this process which has created all the individual conditions. How do we prevent this? We cannot manually update hundreds of modules for each website we need to migrate, and if your migration process does not properly set up conditions then what do we do?

In addition, we have tested the single condition assignment on our fresh J4 and it still impacts other pages. Creating 10 modules with the same condition adds 30 queries to every page.

This isn't acceptable at scale, please advise.

A week or two is a quick fix in my book! Thanks very much Peter, please let me know if you would like any further access to anything. Will leave your access to the 4200 query site in case you'd like to try anything there.

Please keep us in the loop

Thanks

Hi Peter

Thank you for this. While this version has certainly addressed some issues, I unfortunately think this may still be unusable for us.

We reset our test site and followed your instructions. The upgrade now produces ~2100 queries on the homepage, down from 4200. These 2100 queries are still using a lot of memory and response time is sluggish. ~59-66MB mem to execute the queries and they complete in 0.8s

We tested adding modules to other pages and while the impact site-wide is less, it still adds queries to other pages.

Do you think this is "as good as it's going to get" ? I still keep coming back to the fact that Joomla core module manager doesn't need to check every module/condition/rule. I appreciate the differences between it and AMM but surely there's some middle ground - having thousands of queries on every page now seems unavoidable for large sites using AMM. What are your thoughts? Your access has been left on our test site if you'd like to take another look. If we've misused or misconfigued something I would welcome a correction.

Right now I think we're going to have to sadly ditch AMM (after years! :'( ) and write our own plugin to build on joomla's module manager since it is more performant at scale. I would much rather keep using AMM if there's a way around this that is beneficial to all your users.

Thanks again for your time and help Peter.