-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.x]: Multiple duplicate queries for multi-site installs #11113
Comments
We just found and fixed a couple areas where we found a lot of duplicate queries in 3.7.40. Can you post examples of queries you’re seeing a lot of duplicates for? |
sure, this is one of the most problematic, as its the one that takes the longest to execute and also duplicates for each site:
|
That query should no longer show up as duplicated when saving entries in 3.7.42 and onward. If you don’t mind, I’d appreciate if you could test it out, and see if it makes a noticeable improvement on your site. To do that, change your |
applied, but hard to tell if any improvements as ive since switched to mariadb with query caching. (which has had a massive increase in performance by itself) |
Going to close this then. Let me know if you come across any additional expensive duplicate queries. |
3.7.42 is out now with those improvements. |
What happened?
When multiple sites are used, particularly with feedme (but possibly on standard save behaviour) the same queries are used for EACH site when saving an entry. If an entry is saved to 20 sites, the amount of duplicate queries is huge, pointlessly making the same query over and over again.
In MySQL 8, theres no query cache so performance is not so good. Where there is a query_cache, for example in MariaDB, the performance is increased astronomically.
Craft CMS version
Craft Pro 3.7.40.1
PHP version
8.1
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: