Skip Navigation

Home › Support › English Support › [Resolved] My data base is too large with icl_translate

[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.

Tagged: 

This topic contains 1 replies, has 1 voice.

Last updated by Andreas W. 3 months, 3 weeks ago.

Assisted by: Andreas W..

Author Posts
March 12, 2025 at 5:34 pm #16808748

ericH-23

Thank you! Yes, but it was around 400 MB before and now it's currently 1 GB—it even went over 2.1 GB at one point. But the issue should hopefully be resolved soon. I've had over 500 pages (including translations) for a while now, and the table was always around 400 MB. I can't say for sure whether this change was caused by the new WPML version (have all customers this problem now?) or my editor adjustments, as both happened at the same time.

Thanks again, and all the best!
Eric
March 12, 2025 at 6:10 pm #16808845

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

If the posts have 400MB, then our tables might take this amount 3-4 times as we need to save the content various times, to build the connection between languages on our custom tables.

This means on our table we once save the original content, then the translation, and in some cases even the string packages (for example if page builders or Gutenberg are used).
March 12, 2025 at 6:53 pm #16808954

ericH-23

Hi Andreas,

Thanks! I just want to clarify for better understanding: In my system, I also have some custom post types, but the standard post type and meta table take up 150 MB. So maybe that's why the 'icl_translate' table was 400–500 MB (now 1GB regarding the error). Is that what you mean?

Kind regards,
Eric
March 13, 2025 at 1:26 am #16809579

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

To measure the size of our tables you need to consider the sizes of wp_posts and wp_postmeta and multiply them by 3x - in some cases, it might even be a multiplier of 4x if string packages are involved like when using Page Builder.