[Resolved] My data base is too large with icl_translate
This thread is resolved. Here is a description of the problem and solution.
Problem: The client experienced a significant increase in the size of the icl_translation table after switching from Elementor to Gutenberg/GeneratePress, causing delays in staging software due to the large database size. The client also inquired about the creation and loading of .mo files for translations. Solution: We can offer installing a special plugin to manage and delete unnecessary jobs that may be enlarging the database. Our developers are aware of this issue and are working on a solution in a future version of WPML.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
0% of people find this useful.
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.
<b>Background of the issue: </b>
I switched from Elementor to Gutenberg / Generatepress and my icl_translation mysql table changes in one week from ~288.825 InnoDB utf8mb4_unicode_520_ci 371,2 MiB to ~2.323.165 InnoDB utf8mb4_unicode_520_ci 2,1 GiB. Now my staging software needs a huge time and blocks my development.
<b>Symptoms: </b>
My database is too large with icl_translate, causing staging software delays.
<b>Questions: </b>
What can I do to reduce the size of the icl_translation table?
Our developers are still looking into a general solution for this problem, but I can offer to try to clean up the tables as much as possible on your live site.
I would like to request temporary access (wp-admin and FTP) to the site to investigate the issue further.
The required fields are below the comment section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please make sure to back up the site and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and site login details will be set to "PUBLIC". DO NOT publish the data unless you see the required wp-admin / FTP fields.
The private reply form looks like this: hidden link
The next time you reply, click on "I still need assistance".
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We are not allowed to access any credentials that were not specifically submitted on this ticket in the private response form.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
It seems that I am not allowed to access the database on your server using a plugin, but I have temporarily installed our clean-up plugin and removed old jobs from those tables.
Further, I will need to ask you for more patience, as our developers are still working on a solution for this known issue.
Thanks a lot! The current size of the icl_translations table is now 11 MB, wow, that’s a huge improvement! It was over 2 GB before. Great job! Can I do the same if it would be needed again, so may I ask, what you did?
Let’s hope this issue is permanently resolved soon.
Did you also check the WPML settings for resource optimization? And at the end of the development phase, will I need to use .mo files to ensure translations are loaded from files rather than the database?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
We do have a special plugin that we can install in such cases and then delete the jobs.
If you see that the tables grow again, then please let us know and we will assist you.
Regarding .mo-files:
This is a performance factor. Those machine language files are saved inside /wp-content/languages/wpml with the purpose of making your string translations load faster. I would always suggest running the dialog to create such files in case such dialog appears.
Regarding .mo files:
In the settings, I now see the message:
WPML could not detect the translation files (.mo) for ...
So I need to switch to a second language in the frontend. Will the .mo files be created and loaded automatically in this case, meaning I don’t need to do anything manually?
I remember that an older version of WPML had some manual options, but I didn’t fully understand them at the time.
Important:
I followed WPML’s instructions and scanned for new strings, but now the icl_translations table has grown back to over 1 GB – so the issue returned quickly.
You still have the credentials, and they are still working. Could you delete the unnecessary entries again?
How can I prevent the icl_translations table from growing until WPML improves this issue?
Should I avoid scanning for new strings in WPML?
Or was it the other yellow notification asking me to visit the site in a second language that caused icl_translations to grow again?
Is there a way to keep the table size small over the next few days while I continue working, until an improvement by WPML?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
If you scan for new strings it will register all strings of the plugin to the string table.
If you go to WPML > Support > Troubleshooting you will find options in the bottom section to clean up the string table.
Auto-register strings will automatically only register those strings from Frontend that actually need a translation. You will not need to additionally scan themes and plugins for strings.
Regarding the .mo-file dialog:
I have not have this situation yet since the latest major update, but usually, a dialog should show up in the top section of WPML > Theme & Plugin Localization in case such files need to be created.
If you do not see such a dialog, then all the needed files do already exist.
Once the files are created, then any update that you make on WPML > String Translation will automatically update these .mo-files.
Hi Andreas,
Ok, the topic with the mo-files is clear now, thanks!
I used this now:
"If you go to WPML > Support > Troubleshooting you will find options in the bottom section to clean up the string table."
But unfortunately the 1 GB remains.
So what now? Is there a possibility that you clean this again together with an advice for me that the icl_translations table keeps small or is there no chance to keep it small with further working in the site and I have only to wait for an improvement?
Hi Andreas,
Excuse me but I don't understand, what I shall do with "delete the string manually"?
I only got the message wit automatically creating of the mo-files by visiting in a second language and scanned new due to WPML note. Nothing more, so I don't know what shall I do now.
I need to have the icl_translations back to 11mb, now it is 1 GB, if it possible.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
You said:
"I followed WPML’s instructions and scanned for new strings, but now the icl_translations table has grown back to over 1 GB – so the issue returned quickly."
Once you scan for new strings it will add string to WPML > String Translation.
I do not really see a connection between this and the icl_translations table, but I am about to take another look at the site now.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I have now installed the clean-up plugin again and left it on your site for further purposes if cleaning old jobs from those tables.
You will find the options at Tools > WPML Delete Jobs. As yu can see here, there are currently no more jobs that could be deleted, which means that the entries that are currently on your tables refer to existing translations and those should not be deleted.
Our developers are working towards keeping the sizes of these tables smaller in a future version of WPML.
Honestly, while working on my tax preparation—**huii**—I must have mixed things up in my last messages. Now I see that the issue lies with `icl_translate` and other elements, not with `icl_translations`. Also, I noticed that the **2.2 GB from yesterday have decreased to 1 GB today**, starting this morning after your first optimization (which was applied to a staging site that had been set up and left unattended). At that point, it had already reduced to about 600 MB.
So, my final question on this topic for today: **Is there a way to reduce the size of `icl_translate`?**
If not, I can wait for further improvements. This is just a question to ensure I can continue working with staging sites. In my system, handling larger databases takes too much time and eventually stops after several hours.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
The more translations you create, the bigger icl_translate will get and I saw that your site has more than 500 pages. In a future version of WPML, our developers will try to keep this and other tables smaller but at the moment this is expected.
