Translations should be saved using operations to avoid exeeding memory or time execution

Created on 28 January 2025, 2 months ago

Problem/Motivation

Currently Deepl calls are done through batch operations but all translations are saved at once in the batch finished method.

This leads to memory and/or maximum execution time errors.

Steps to reproduce

  1. Ensure you have a normal memory limit and max execution time (for example 512m and 30s).
  2. Translate a content having ~20 paragraphs using the batch system with ~40 target languages.
  3. See that the batch will stop with errors after saving 5 or 6 translations.

Proposed resolution

Use operations to save translations so the batch system will handle the memory and time management.

Feature request
Status

Active

Version

2.2

Component

Code

Created by

🇫🇷France Nixou Toulon

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Nixou
  • 🇫🇷France Nixou Toulon
  • 🇩🇪Germany SteffenR Germany

    Good point and thanks for the finding. I just did a test with lots of content and multiple languages and its working fine for me.

    But it still needs work, since we loose the display of the translation messages, which are shown after the batch has run.
    If translation job need review afterwards, the messages would look as following:

    It would be great, if you could update your patch or even create a merge request with the changes.

    Thanks so far.

Production build 0.71.5 2024