Okay. We already tested the two suggested scenarios with the custom theme and all the plugins. Sometimes it shows an update failed error, mostly on large pages that have already been translated into other languages.
Regarding the autoload data, what will we do then? When we contacted the WP Engine support team, they had a limit on the autoloader data, which is 800 kb, and ours is more than 1.2 Mb. They also told us this would be the main issue with slowness. When we checked with the WP engine, they said there was no option to change the limit, and they asked us to contact the plugin team. So we contacted the WPML team, and they said they need these options to be loaded automatically, and if we turn them off, the WPML plugin won't work. What will we do then? How can we fix this autoload issue?
Top largest autoload rows:
mysql> SELECT LENGTH(option_value),option_name FROM wp_options WHERE autoload='yes' ORDER BY length(option_value) DESC LIMIT 20;
right? Can we proceed with that? Are you sure that won't lead to any issues in the future? If you can give a confirmation, we can make the changes ASAP.
Thank you; that would be helpful. We only need to make sure that in the future the plugin works properly without any issues after we disable autoload options for the mentioned tables. Also, please ask them to list out the database options that we can set its autoload to "no" from the WPML plugin.
I have checked and this is the current status and explanation:
autoload = no, fire SQL each time, autoload = yes save the data in PHP memory and loads on the first page
icl_sitepress_settings should not be removed from the autoload as this is frequently used everywhere in the WPML and add-ons and will call SQL queries too many times then
otgs-installer-log can be removed from autoload since it is just logs.
About others, we suggest testing first if it affects your website in any way, but if you see improvement after the changes and setting autoload to NO then autoload should not affect the functionality. To be honest we are also working on this case and going over each option making improvements and making sure they need to be autoloaded or not. I will update you when I have more news, but this process will take time and I am afraid this is the best we can suggest for you now.
Hope this makes sense, let me know how it goes and if you have any other questions.
Okay, we will remove "otgs-installer-log" from the autoload. We will check the other 2 remaining options (ATE_RETURNED_JOBS_QUEUE, otgs_active_components). Since we are not aware of how these options are working with WPML, it is a risky task to disable these unknown options from autoload. Please check it on your side too, because you have more knowledge of the mentioned options and how they are connected with WPML.
I am happy to hear that you guys are working to improve the database. Please do it ASAP, because many people face this same autoload issue on their website too. Almost all the highly loaded options are from the WPML plugin. It would be great if you could find a solution and fix this autoload issue as soon as possible.
thanks, as said setting those two also to autoload NO, should not cause any concern in the functionality of WPML, the difference would be in SQL queries only, which then can also affect your performance / load.
I suggested you test this, since I can not be 100% sure, as this is being still tested and debugged from our side what is the best approach here.
I understand your concern and we are working on this, but this won't be very soon and will take some time. For now it is scheduled for WPML 4.7. I will update you when I have more news.
