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.
This topic contains 3 replies, has 2 voices.
Last updated by Bobby 2 years, 5 months ago.
Assisted by: Bobby.
Author | Posts |
---|---|
June 9, 2022 at 10:54 am #11423613 | |
pascalB-53 |
Hi, I need some help. I need to optimize wp_options table and more precisely the autoloaded data. I see some records from WPML with large size Do they need to be loaded automatically. Thank you! |
June 10, 2022 at 4:44 am #11430217 | |
Bobby Supporter
Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00) |
Hello, These records are needed for WPML to function properly as they hold information regarding your installation. We recommend against making any changes to these fields. You can go to WPML->Support->Troubleshooting->Cleanup and Optimize String Tables. This action will help remove any bloat from the database. Database tables documentation: |
June 10, 2022 at 7:12 am #11430815 | |
pascalB-53 |
Thank you for the answer! I tried this optimization but nothing has changed. The size is really big. It is clear to me that this data is needed. But my question is do they need to load automatically every time? |
June 10, 2022 at 8:02 pm #11436777 | |
Bobby Supporter
Languages: English (English ) Timezone: America/Los_Angeles (GMT-08:00) |
Unfortunately, the data needs to be autoloaded in order for WPML to function so in short it is not recommended to turn autoload off. a longer format answer as to what this is related to: I can see you are using wp engine which has a known issue regarding the size of autoloaded data. The issue happens due to WPEngine performance autoload data limitations. I am sure if they check logs they will see cron removed these tables due to their larger size. I am sharing more info and a reply from WPEngine from a related ticket: To answer WPMLs question is that we do remove large options from a database with a daily cron that runs. In our environment, a large option is defined as having more than 1MB for autoload content and 4MB for non-autoload content. Rows in wp_options with autoload set to "yes" are considered large at 1MB because all of it is loaded up on every single page load. Related links: |