Skip to content Skip to sidebar

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.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 14:00 10:00 – 14:00 10:00 – 14:00 10:00 – 14:00 10:00 – 14:00 -
- - - - - - -

Supporter timezone: Asia/Kolkata (GMT+05:30)

Tagged: 

This topic contains 3 replies, has 0 voices.

Last updated by Sumit Singh 16 hours, 7 minutes ago.

Assisted by: Sumit Singh.

Author Posts
February 19, 2026 at 6:36 am #17834363

peterJ-48

Hi Sumit

5) Big database tables.
Prakash tried to run the job you suggested, but it did not seam to fix the issue. Please see his mail from 16 Feb.

Best regards
Peter

February 19, 2026 at 7:07 am #17834422

Sumit Singh
WPML Supporter since 12/2025

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi Peter,

I run the WPML > Support > DB optimization again on the staging site to make sure it is completed correctly.
After that, I also need to run the MySQL table optimization, which is an important part mentioned on the box and our docs too https://wpml.org/documentation/support/wpml-tables/optimizing-wpml-database-tables/

While the optimization reduces the amount of data in the tables, it doesn’t shrink the disk file. Reclaiming disk space would require manually rebuilding the tables, which is not part of this process.

And I can see a huge difference in table sizes.

icl_translate went from 900MB to 458MB
icl_translate_status went from 843MB to 28MB

I have also sent an email to Prakash.

Thanks

February 23, 2026 at 4:06 pm #17843817

peterJ-48

Keep ticket open

February 24, 2026 at 11:40 am #17846266

Sumit Singh
WPML Supporter since 12/2025

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi Peter,

I think this issue is resolved we can close this ticket?

Thanks