This thread is resolved. Here is a description of the problem and solution.
Problem: The client is concerned about the high percentage of autoload data related to WPML in their database, questioning the necessity of autoloading certain entries like 'otgs-installer-log' and '_wcml_settings', and expressing concerns about the overall impact on website performance. Solution: We explained that the autoload entries are essential for WPML's functionality and should not be disabled. Although we are continuously working on performance improvements, these entries must remain as they are for now. We clarified that the size of these entries, such as 'icl_sitepress_settings', is relatively small (approximately 3.6 KB) and typical for plugins storing extensive settings. We suggested that the client tests their website's performance with and without WPML using tools like Page Load Time to gauge the actual impact. Additionally, we referenced a similar case discussed in our forums which might provide further insights: WPML forum discussion.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
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.
Background of the issue:
I am trying to optimize my database and autoload tables.
Symptoms:
WPML is taking up almost 50% of the load of the complete website.
Questions:
Is it really necessay to autoload all these database entries for WPML, and are you going to optimize this is the near-future?
icl_sitepress_settings 29199
icl_st_settings 20869
otgs-installer-log 9759
wpml_shortcode_list 7599
WPML(ST-MO) 5575
otgs_active_components 3755
wpml_update_statuses 2884
wpml_strings_need_links_fixed 2870
wpml_language_switcher 2862
_wcml_settings 2647
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
Hi,
Thank you for contacting WPML support!
Yes, these entries are needed for WPML to function, you should not disable the autoload for them. We keep working on performance issues, however as of now you can't disable them. Note that this is 29199 bits which is approximately 3.6 KB so in most contexts, such as WPML options, this amount of data is minimal and not considered large.
The biggest of them - wp_installer_settings - is not autoloaded at all.
I am sending you comparison from my localhost where you can see there are many plugins that autoload much bigger chunks of data yet have probably little influence over the site load. The heavy processing or data fetching (like form submissions or backup files) happens only when needed and is not autoloaded.
thank you for your explanation. Yes, I realize it it not that many bites, but overall it just seem sloppy? Why do you need installer logs etc in an autoload? I don't understand, can you please explain?
And in the end, after optimizing many others, you still take 50% of the total autoload! Seems quite excessive.
All file name that I send you are autoload, including the ones with installers.
Specifcally, why are these autolaoded?
otgs-installer-log 9759
And I think you refer to _wcml_settings 2647?
Attached a screenshot of the top10 autoload, and see how much is wpml
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
How big it is is less important than how does it affect your website. Because we cannot reduce it - for example icl_sitepress_settings will store all your WPML settings, for example custom fields preferences. The more you have, the bigger this file will be, just as with any other plugin.
Can you test your website performance with and without WPML using tools such as hidden link and send us the results?
In this topic i read that the otgs-installer-log indeed does NOT need the autoload option, and also that it will be addressed and updated in future releases. This was february, we are almost 8 months further ahead. Why has this not been addressed?
Did it turn out there was an issue after all with turning this off? Or have you not updated a rather straightforward variable after 8 months of updates?
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
Not many clients reported this as an issue so it hasn't been prioritized, changes on the matter may end up in WPML 4.7 but I can't give any other details.
That particular client never gave feedback whether it caused some trouble on their site, if it was the case they would report back though.
