This thread is resolved. Here is a description of the problem and solution.
Problem: Reduce icl_translate table size
Solution:
1. Download and activate the WPML Delete Jobs plugin.
2. Visit Tools → WPML Delete jobs
3. You will see a text area prefilled with job IDs, these are 50 suggested job IDs to delete first. These job IDs are the same that you will see in WPML → Translation Management → Jobs. You can uncheck some job IDs in case you don’t want to touch a few pages or posts.
4. Click Delete and wait. Once the content is deleted, you will see a new batch of 50 IDs to delete, and so on until there are no jobs for revision.
5. Finally click on Optimize _icl_translation_status table to reduce the size of icl_translation_status table.
6. Deactivate and remove the cleaning plugin.
While cleaning up my database, I have noticed that two WPML tables were taking 67% of my entire database size!
* icl_translate: 270M
* icl_translation_status: 45M
This usage is way too high for such a small site. What can I do to reduce these two table sizes?
Hi there,
Good morning! If you're dealing with a large amount of data in your posts and postmeta tables, and you're using either a page builder or the Gutenberg block editor, the WPML Delete Jobs plugin can help reduce the size of your database.
⚠️ Important! Please make a full site backup (files and DB) before you proceed with those steps. ⚠️ ** If your site is a live site, you might want first to try those procedures in a staging environment or a snapshot of your site on your local server or another server. **
Thanks for the quick answer (on a Sunday!). I have used this plugin and made a backup before and after. It looks like it worked well for the icl_translate table. It was reduced from 270M to 55M, reducing my entire database size by 50%. I have not seen any changes in behavior and checked a few translations.
I am not using any page builder or the block editor, but this plugin still helped!
The icl_translation_status is still 44M after this update, does that sound reasonable or is there still some opportunity for reducing that?
Hi there,
Good afternoon! I'm delighted to hear that the plugin significantly reduced the size of your icl_translate table - that's fantastic news!
Regarding the icl_translation_status table, it's normal for it to remain larger even after optimization, as this table typically stores information about the status of each translation, such as whether it has been translated, is in progress, etc.
Don't worry about the database optimization for now. If the table size increases further, you can try the plugin again.
In the meantime, please don't hesitate to reach out if you need anything else.
Hi,
Great to hear that the issue has been resolved! If you require any additional assistance in the future, please do not hesitate to open a new ticket.
