Hello,
wp_installer_settings is 126 KB in size for us.
We would also like to see an improvement!
We have opened numerous tickets in the past and are only making slow progress. WPML causes us the most trouble in terms of tickets, debugging, and error frequency in our WooCommerce online store.
WPML has improved in the past. Nevertheless, I would appreciate a higher level of commitment to performance and code quality.
Could you please confirm whether this has been fixed, or if it’s still pending?
A confirmation would be great news (and then an update of the related erratum + mention in the changelog).
And if not, an update here would still be better than no update at all.
That is great news; after a very long wait the expectations where quite high.
I need to run some more debugging / tests, but at a first glance it indeed seems the autoload database is considerably smaller. Especially the 'wp_installer_settings' is now not showing up anymore as the single biggest autoload setting.
There is still some considerable autoload going on, is this really necessary for WPML?
- icl_sitepress_settings
- _icl_cache
- wpml_strings_need_links_fixed
- wcml_currency_switcher_template_objects
- wpml_shortcode_list
- wpml_language_switcher_template_objects
- WPML(ST-MO)
- wpseo_taxonomy_meta
Some, if not most of these, seem unnessary to autoload by default? Why do you need current switcher template etc?
Or are there still things i need to update/run after updating all the plugins?
Some level of autoloading is expected and necessary for WPML to work correctly. In particular, settings related to language handling and the language switcher need to be available on every page load, since multilingual logic and the switcher itself are used site-wide. Autoloading these avoids repeated file lookups or recalculations, which would otherwise hurt performance.
That said, the amount of data being autoloaded should stay within reasonable limits. The reduction you’re seeing (especially around wp_installer_settings) is expected after the update.
There shouldn’t be any additional update steps required beyond updating all plugins. If autoload size still seems unusually high after this, the next step would be to review the site’s specific configuration to confirm everything is behaving as expected.
Thank you for the improvements. I appreciate this has been taken care of
From my understanding, at least within the WordPress environment, autoloading is beneficial when the data is required on every page load or on key pages (e.g., homepage, SEO-focused content, etc.). However, autoloaded data is loaded on every request — including backend pages, AJAX calls, cron jobs, and other processes — whether it is needed or not.
As a result, the more autoloaded options there are, the greater the impact on TTFB and the higher the memory usage per request.
In short, while it may be tempting to autoload many options for convenience, this is often not ideal. Each website has different needs and should carefully evaluate what truly needs to be autoloaded. WordPress generally recommends keeping autoloaded options under 800 KB.
I reviewed my wp_options table and noticed multiple WPML (and add-on related) entries set to autoload (or eligible for autoloading). I haven’t updated to the latest version yet, and I understand that this may already address part of the issue. However, if the only recent change concerns wp_installer_settings, I believe there may still be room for optimization.
In my case, there are 85 WPML-related autoloaded entries. At first glance, some of them seem difficult to justify as autoloaded, for example:
- _wpml_jobs_not_notified
- wpml_strings_need_links_fixed
- otgs-installer-log
- wpml-updates-log
- _transient_wpml_admin_text_import***
While some of these options are small in size and individually, have a small impact, the broader concern is cumulative impact. If each plugin does not carefully manage autoloaded options, this can significantly affect overall site performance.
Can you explain if, and why these options are required?
In my situation, I am approaching the recommended 800 KB threshold. For websites that use WPML more extensively, or many plugins, optimizing autoloaded options could have a meaningful performance impact.
Hello everyone, I have been following this topic closely since the beginning because I am also affected by this issue.
I am chiming in because I would like to say how much I agree with T4ng's last message.
Indeed, large WooCommerce sites with many plugins are significantly slowed down by the use of WPML.
Optimizing the preloaded options would be really beneficial for sites like ours.
The topic ‘[Closed] wp_installer_settings is autoload and large’ is closed to new replies.
