[Closed] 504 Error when there's a lot of people working on the translation

Hello,

Before we do this changes on the website, I want first to understand better the context of where the issue is coming from and be able to be sure about it since we had a lot of experiences of testing solutions from WPML here and there.

There are two linked issues we have now been experiencing for quite some time:
1. 504 Issue
2. Slowness of the plugin when a lot is translating at the same time

The flow is that it would take time to load the changes we do with WPML and eventually will lead to a 504 issue.

We have reached out already regarding Issue #2 in our previous ticket which is slowness and one of your support recommended that we whitelist the ff domains: (wpml.org, api.wpml.org, ate.wpml.org, ams.wpml.org) However, upon further investigation it doesn't make sense on our end since we're not blocking any of these domains. But it only leaves us a question that maybe it's not within our database that we should look at maybe we have to understand your infrastructure side on the allotment of database we get from you.

Question #1: When we translate, or do anything using WPML, how does the request process be? Is it being processed by WPML server/database or OUR server/database?

Since we have been receiving solution in fixing our database but we're not really sure if this comes from us alone.

For Issue #1 - 504 Error, this is where you already helped us with and I wanted to give you more information regarding about it before testing your solution.

Earlier, our Infrastructure team investigated further where the 504 issues are coming from and they wanted to get information from WPML support about high database utilization when several people work simultaneously. Please see attached image regarding the high database utilization record we got.

It seems there are 1131 requests to generate a “Page” every time per user. Other issues are likely related to high database load (almost 100% CPU).

We also have a lot of similar issues found on the debug log we did last week. I can share this with you if you can activate the private and sending debug log feature.

I know that this is a lot of information and there are two things I'm pointing out but they are similar with each other and I wanted to tell you all this to expect a better response from WPML Support please. We can't just do and test everything here and there, I wanted a solution that has context and understanding as to why this is happening. Ever since we used WPML we had a lot of issues here and there that points to different parts of our WP set-up. We did a lot of numerous solutions from you already, which are all quick solutions.

Can we please point out where exactly this problem or issue is coming from so we can really do a solution for long term basis and not just something quick that we test and then after won't work or would leave our Infrastructure team questioning the solution from you.

Thank you

Hello,

Sorry for the late response.

I would like to better understand the process of translation using WPML based on the details you mentioned:

1. "If you use the Advanced Translation Editor, the prepared content will be sent to our server (XLIFF file) and you/translator/user start translating in the editor."

- Does it mean the process start with:
> Every page/post we created is being stored in your server/database first?
> then once this content is stored, it will now be available for translation using ATE

2. After completing, the translation content (XLIFF file) will be sent to your site
> Once the complete button is clicked, WPML will store this translation again in your server/database
> then you will sent us this file and this will be the only time that the translated content will be stored in our system

To simplify, the whole process is something like this:

Page/Post Published > Saved it on WPML Server/DB > Content will be available in ATE > We add translation > Saved it again on your Server/DB > Sent the XLIFF File to our website > XLIFF file is saved on our system > Page/Post is created/updated.

Thank you!