Home›Support›English Support›[Escalated to WPML Developers team] Large autoload data causing slowness on WP Engine
[Escalated to WPML Developers team] Large autoload data causing slowness on WP Engine
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
We're still seeing the issue. We have a site where 3 WPML settings are autoloaded and account for 1,130,166 bytes or 1.13mb that is loaded on every query. This makes the site extremely slow and is well over WP Engine's recommendation of less than .8mb of autoloaded data. hidden link
Here are the top 3 settings. But WPML makes up 8 of the top 10 autoload data options on the site.
icl_sitepress_settings - 443033 bytes
_WPML_TP_Pickup_Logger - 442577 bytes
wpml-tm-custom-xml - 244556
It looks to be from a large amount of ACF fields being stored to these options.
I did see a thread that gave me hope this was resolved in an update after we requested the feature in our previous conversation, but installing the latest plugin on a local environment does not seem to have effected the amount of autoload data at all.
I have two questions, has this been addressed in an update and is there anything that needs to be done to refresh the database? We're going from version 4.3.4 to the latest.
And if not, can we change those options to `autoload = no` in order to prevent them from being loaded on every request? This assumes they're properly called in the plugin when the data is needed. Even just being able to set one of the 400mb options to not autoload would get us close to WP Engine's suggested threshold.
Note: Provided debug information is for environment where the plugin has not been updated yet, but as I noted updating the plugin locally has not fixed the issue in the database. We're working to get the approval to update the plugin on this environment currenetly.
thanks for sharing detailed information about your issue.
1) The icl_sitepress_settings is needed almost on all pages. This is the primary option key for WPML.
I would advise upgrading to the latest WPML versions (4.4.4.) since a lot of changes and improvements have been done in the meantime, which can indirectly affect your issue and improve autoload data.
If you still have the same issues please go to the next step.
2) I see from your previous ticket this was consulted with our specialist and it was advised to you to go to "Suggest a feature form" and suggest a change in our products.
Have you followed this procedure and suggested it directly to our developer department?
1.) Does the icl_sitepress_settings need to be autoloaded though? Can it be set to autoload = no? I assume when its data is used it is properly called with `get_option()` but if it is dependent on being autloaded we can leave it.
What about the other two option I listed are they able to be set to autoload = no? _WPML_TP_Pickup_Logger, wpml-tm-custom-xml
As I noted above I did upgrade to version 4.4.4, but it did not reduce the size of the autoloaded data. The issue is the autoloaded data at 1.13mb is larger than the WP Engine recommendation of .8mb to work with their object cache. So any solution that doesn't reduce the autoload data is not going to work.
If there are steps to take in version 4.4.4 to reduce the autoload data size after updating, they are not clear.
2.) I did request the feature, but have not seen it implemented.
