Skip Navigation

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 – 17:00 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 -
- 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 -

Supporter timezone: Asia/Kathmandu (GMT+05:45)

Tagged: 

This topic contains 16 replies, has 2 voices.

Last updated by Shekhar Bhandari 1 year, 10 months ago.

Assisted by: Shekhar Bhandari.

Author Posts
September 4, 2023 at 6:59 am #14333819

fredrikS-7

Hi,
Now I´m back again and will be here the whole week to solve this issue once and for all!

If you try any product page in backend it takes 10-20 sec to open.

Example:
hidden link
hidden link

More or less after trying with several solutions I can just find out that:
WPMLś load on the server is enormous while having query in backend.
Uncoce the Theme has the same behaviour together with WPML.
These two together consumes so much power that my services on my server hit the roof.

Most common issue is the request for wp-admin-ajax and also add -index to that url.

hidden link

This one: hidden link - this url and common to it is a real server killer. 30 sec.

I do not know if above thing is a real problem.
I just know that when I Deactivate - WPML String Translation - it goes better.

My server SHOULD be able to handle this.

CPU 3 CPU +1 CPU =>
RAM 5 GB =>
Disk 30 GB =>
Bandwidth 5 TB =>
IO 250 MB/s

The allowance for OurYogaShop.com is to use 400% of above resources - even then - it hits the roof for the above queries.

Only way I found to get the page going in backend:
Deactivate - WPML String Translation

Then the page runs smooth.

Please check this!

All the best!

Fredrik

September 4, 2023 at 8:35 am #14334525

Shekhar Bhandari
WPML Supporter since 03/2015

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

Our 2nd tier checked the issue and suggested the following:

as_async_request_queue_runner is an action related to the asynchronous scheduled task.
In our experience with similar issues, We've noticed that WP Rocket is responsible for those requests because of the "preload" setting being enabled.

Probably it will help if you try turning that off.

Can you try this and let us know the results?

Thanks

September 4, 2023 at 10:10 am #14335439

fredrikS-7

Hi,
for the speed in the backend it had no positive effect at all.
Only thing that get things going is to deactivate WPML String Translation plugin.

/F

September 8, 2023 at 3:51 am #14363385

Shekhar Bhandari
WPML Supporter since 03/2015

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

Forget to update the status, the issue is now escalated to our 2nd tier supporter.

Thanks

September 8, 2023 at 9:50 am #14365563

Shekhar Bhandari
WPML Supporter since 03/2015

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

The shared file has expired so can you re-share it?

Further, We recently released a new version of WPML plugins so can you please update the plugins to the latest version and let me know if that helps.

We push out WPML releases gradually. If your sites haven’t received this update yet, give it some time and you’ll see the update in a few days.

To skip the queue and get the update right away, to the Plugins → Add New page, click the Commercial tab and then click the Check for updates button.
https://wpml.org/wp-content/uploads/2020/04/wpml-force-plugin-update-1.png

Note: Keep a Backup Before Updating

Could you please update and provide us the links where you see performance issues?

Upon debugging, we found noteable performance with
- Unicode theme
- as_async_request_queue_runner
- Imagify the plugin and its scheduled actions.

So can you disable all of this and see if it helps? Perhaps you should purge the records related to as_async_request_queue_runner in the respective tables too.

Also, can you provide another x-ray report so we can debug this further?

Look forward to your reply.

Thanks

The topic ‘[Closed] Performance Issues’ is closed to new replies.