Peter here. Our developers have analysed what queries that are send to our database. It turs out that from each page the statement show below, is executed multiple times with different element_id. When each statement is executed, it returns 400 rows with only 20 unique rows (and a lot of duplicates).
----
SELECT wpml_translations.translation_id, wpml_translations.element_id, wpml_translations.language_code, wpml_translations.source_language_code, wpml_translations.trid, wpml_translations.element_type
FROM www0_icl_translations wpml_translations
JOIN www0_term_taxonomy tax ON wpml_translations.element_id = tax.term_taxonomy_id AND wpml_translations.element_type = CONCAT('tax_', tax.taxonomy)
JOIN www0_icl_translations tridt ON tridt.element_type = wpml_translations.element_type AND tridt.trid = wpml_translations.trid
WHERE tridt.trid =
(SELECT trid FROM www0_icl_translations wpml_translations
JOIN www0_term_taxonomy tax ON wpml_translations.element_id = tax.term_taxonomy_id AND wpml_translations.element_type = CONCAT('tax_', tax.taxonomy)
WHERE element_id = 8646 LIMIT 1);
-----
This seams to be slowing down our site a lot.
One of our developers has discussed the issue with your colleague Eran Helzer on the chat (please see below images of the conversation). As you can see from the chat this is apparently a know performance issue that is scheduled to be fixed in your next release.
As this is having very negative consequences for our business, I would like to know the following:
1) When do you expect to be ready with a solution to the issue?
2) Your colleague is asking for a copy of our site for further investigation as the performance issue may occur in several forms. It is very important for us to have the issue solved and we would like to send you a duplicator package of our site. The size of our site, when using the duplicator plugin, is 4,5 - 5 GB. I believe your normal sandbox environment has a max of 800 MB. Is there another way we can transfer it to you?
Thank you for the report. I checked our issue tracker and indeed there is a report but there is no ETA for a fix yet.
I suggest that you use the Duplicator package and use the options to remove nig files that you think will not be effective on the whole process of troubleshooting, such as media files.
Alternatively, you can use a transfer online service such as wetransfer or google drive to upload the package and share the link with us.
Please make the next reply as private so you can meanwhile provide the login information for the package that you share.
Is there any update about maybe_populate_cache() issue? actually, it is slowing down our entire website and because of the speed issue, we are losing our business.
During our troubleshooting, we found that maybe_populate_cache() affects each and every record from the database.
For example, we are trying to fetch the "about us" page link from the database, and directly or indirectly maybe_populate_cache() comes to the action and it loads all the elements related to "about us" and those records are around 400 for just one-page link and I have seen around 256 queries with same behavior with different elements.
Please guild if we can disable maybe_populate_cache() from our end until you guys resolve it. Because we are losing business and as you are not able to provide any ETA so the only option left for us.
Thank you for the details. Our development team is aware of the issue and the priority of the issue is now on a high level.
We do understand that you are in a waiting mode here, at the moment nothing else I can share and it is not possible to turn off such a feature as it is an interconnected codebase.
I want to make sure to convey the message that we are fully working on this matter and if I have an update I am going to share for sure.
- Improved translation sync process when a lot of translations are sent with Translate Everything Automatically mode.
- Improved the performance of WPML_Term_Translation and maybe_warm_term_id_cache.
It is not the one that you mentioned in your latest reply about "maybe_populate_cache".
That is still something that our development team work on.
I checked and there is no set release date for that yet.
I do suggest that you update WPML anyways as it will improve the performance in other areas mentioned in the changelog above.
Our developers will try and test the latest release at our staging server as you suggest.
It is absolutely crucial to our business that the issue reported in my message from June 9 is solved. The impact on our business is so negative, that we are forced to start working on an alternative solution to WPML if this is not solved within a foreseeable time. I must therefore ones again ask you to give me some kind of time estimated for when you expect to have a solution ready, so we can decide how to proceed from here.
I double-checked and there is still no set date for a release on the particular issue you have mentioned.
I do understand that you are under pressure and rest assured that we have this as a high priority.
For now, the only thing that the second-tier support could suggest was:
For this issue you can suggest user to have fewer products listed on a single page. i.e. related product, most popular product etc.
If they are using many widgets to display them each product has queries to translate the variations.
Also, using page and object caching there might help.
If you have this as high priority, I also assume that you are working with some kind of plan. I am not asking for a specific release date, but you must be able to give me some kind of time estimate (are we talking 1 week, 1 month or 6 month?), so we are able to plan and decide how to proceed from here.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello!
The performance fixes related to your problem are in track to be included in our next minor release (4.6.6). as Christopher told you there isn't a clear ETA yet because we need to make sure that the fixes successfully pass our internal tests. however it should be coming soon (possibly coming in the first or second week of september, but this date could change!).
The topic ‘[Closed] Performance issue’ is closed to new replies.
